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

Adds meaningful behavior beyond the annotations: queued jobs refund the reservation in full, while running jobs stop at the next trial checkpoint and charge only completed work. This billing/execution nuance is not present in the annotations and materially helps an agent predict consequences. No contradiction with readOnlyHint, idempotentHint, or destructiveHint.

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?

Two tightly packed sentences: the first states the purpose, the second explains the caveats. No filler or repetition; every clause earns its place.

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 simple single-parameter cancellation tool, the description covers the key operational outcomes (queued vs running). It does not mention how to retrieve jobId or what happens if the job is already completed, though the idempotentHint partially mitigates repetition concerns. The low complexity keeps this close to 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 zero parameter description coverage and the tool description never mentions jobId or how to obtain/validate it. The parameter name makes the meaning inferable, but the description does not compensate for the lack of schema-level documentation as required by the low coverage.

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 ('Cancel') and a specific resource ('one of your background research jobs'), which clearly differentiates from sibling tools like ata_cancel_research_task and ata_cancel_research_workflow. The phrase 'background research jobs' pins the scope precisely.

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?

Provides clear context that this tool is for cancelling background research jobs, not tasks or workflows, and clarifies behavior for queued versus running jobs. It does not explicitly name alternative tools or state when not to use this one, but the resource type alone gives adequate selection guidance.

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