Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructiveHint=true, but the description goes well beyond them: it specifies exactly what is destroyed (stored events), what survives (retained receipts stay verifiable), the cost/auth model (free, no account), the side effect (records a GAIP receipt), and an input constraint (public, non-personal). This is unusually rich behavioral disclosure for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the trigger condition, then the required inputs, then the destructive/retention semantics. No filler and no repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, two-parameter tool with nested inputs and no output schema, the description covers the trigger, the required arguments, destruction scope, retention behavior, cost/auth, and input constraints — everything an agent needs before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already documents both watch_id (returned by gaip_watch_register) and continuity_handle (proves ownership). The description restates that both must be passed but adds no format or edge-case detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — stop/remove a watch on an agent or service — and pairs it against the register flow via the required watch_id, so an agent can tell it apart from gaip_watch_register or gaip_watch_list without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this when asked to stop watching an agent or service" gives an explicit trigger condition. It does not name a when-not case or explicitly contrast with gaip_watch_list (view) versus this removal tool, so the guidance is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.