Glossary · Tool annotation

Tool annotation

A tool annotation is a declared property of an MCP tool, read-only, destructive, idempotent or open-world, plus a human title, that a client shows the person before they approve a call. IZeat annotates every tool without exception, and derives the hints from the tool's declared effect so they cannot drift from the code; a test fails when a registered tool has none.

The annotations are what let a client ask for the right amount of vigilance: reading a day is read-only and can be approved once and remembered, deleting a meal is destructive and deserves a look each time. A customer taught to approve everything without reading is a customer who misses the one call that mattered, so the reading tools must not ask for the same attention as the writing ones.

Annotations are a small thing that decides how a product feels inside an assistant: with them, the everyday writes can be approved once and the conversation flows; without them, every call interrupts, or worse, none does. IZeat's reviewer guide and demo follow the annotations, and the two everyday writes, logging and updating a meal, are the ones a customer is invited to remember the approval for.

Updated

Other glossary terms

← Glossary index