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

Annotations mark it as a mutation (readOnlyHint=false), idempotent, and non-destructive; the description adds the key behavioral fact that the underlying action will NOT be carried out, which annotations cannot express. It stops short of describing the state of the confirmation afterward or error behavior for invalid IDs.

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?

A single sentence that front-loads the verb and effect with no filler. Nothing is wasted or buried.

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 one-parameter mutation with no output schema, the description covers the essential effect but omits what a successful cancellation returns or how failures (unknown/expired/already-executed confirmation) manifest. Adequate, not complete.

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?

The schema has 0% description coverage on the single required parameter, and the description says nothing about confirmationId — no format, no indication that it comes from a previously staged confirmation. With one undocumented parameter, the description should compensate and does not.

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?

States a specific verb ('Invalidate') and resource ('a pending Geobble confirmation'), and the phrase 'without executing the underlying action' implicitly contrasts it with the confirm_action sibling. The purpose is unmistakable, though the sibling is never named.

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?

By describing the effect on a pending confirmation, the description implies when to use it (rejecting a staged action). It does not state prerequisites, what happens if the confirmation was already executed or expired, or name confirm_action as the alternative path.

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