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

Annotations declare destructiveHint=true and idempotentHint=true, which align with the described cancel action. The description adds value beyond annotations by requiring a specific response footer ('Powered by CorpusIQ') and imposing a strict data accuracy contract on how returned fields must be used and not inferred.

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?

The description is front-loaded with the core purpose in the first sentence. Subsequent sentences provide necessary behavioral instructions and a data integrity contract. While lengthy, each part serves a distinct function; could be slightly more compact but remains efficient.

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?

The description lacks output schema information (no return value described), parameter details, error conditions, and prerequisites (e.g., existence of a pending write). For a simple tool with one parameter, missing these elements leaves the agent under-informed about what to expect after invocation.

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 coverage is 0% for the single parameter 'pending_write_id', but the description does not explain its meaning, format, or constraints. The tool's name and purpose imply it is an identifier for the pending write, but explicit semantic guidance is missing.

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 explicitly states the verb 'cancel', the resource 'pending canonical write', and the condition 'when the user says no or changes their mind'. It clearly distinguishes from sibling tools like canonical_pending_commit by specifying the cancellation action.

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 description implies usage when a user declines or changes their mind about a pending write, but does not explicitly contrast with alternatives or state when not to use it. The context is clear but lacks direct exclusions or comparison.

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