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

Annotations already declare destructiveHint=false and idempotentHint=true, so the agent knows this is a safe, repeatable mutation. The description adds one genuinely useful piece of context beyond that: the underlying action is not executed. It stops short of covering auth requirements, error behavior for unknown/expired confirmation IDs, or the effect on the pending state.

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?

One front-loaded sentence with zero filler; the scope-limiting clause ('without executing the underlying action') is placed where it matters most.

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 single-parameter cancellation tool whose annotations already carry the safety profile, the description is minimally adequate. The gaps are the parameter's origin/meaning and the failure/edge-case behavior, neither of which exists in an output schema or in the schema itself.

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 0% and the description never mentions confirmationId at all, so nothing clarifies where the ID comes from or its expected format beyond the type and length bounds in the schema. For a required, 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 a precise resource (a pending Geobble confirmation), plus the key scoping fact that it does not execute the underlying action. This implicitly distinguishes it from the sibling geobble_confirm_action, though it never names that alternative directly.

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?

The word 'pending' implies a precondition, but there is no explicit when-to-use guidance, no statement of what happens if the confirmation is already executed or expired, and no routing to geobble_confirm_action as the opposite choice. Usage must be inferred.

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