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

With annotations already declaring destructiveness, idempotence, and non-read-only status, the description adds concrete behavioral effects: it releases unspent reservations, is free, does not refund or delete completed paid results, and leaves archive data, Lists, and other accounts unchanged.

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 action and scope, then efficiently states cost and side-effect boundaries. Every sentence adds useful information without repetition.

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?

Given the output schema exists and annotations cover safety traits, the description is nearly complete for the cancellation behavior. It omits how to obtain the operation_id, which would help an agent invoke it correctly.

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 does not mention the sole required parameter operation_id at all. It therefore adds no semantic meaning beyond the schema's type and pattern.

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: 'Cancel an owned queued or running research request.' This clearly distinguishes it from sibling read/list/recover tools.

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?

It specifies the applicable state ('owned queued or running') and clarifies that completed paid results are unaffected, giving clear context for when the tool applies. It does not explicitly name alternatives for cancellation or recovery.

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