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

Beyond the annotations (destructive, idempotent, openWorld), the description discloses the key asynchronous trait: running provider work may continue until cancellation is confirmed, and a polling timeout does not cancel work. That is exactly the non-obvious behavior an agent needs and the annotations cannot convey.

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 sentences, zero filler, with the action stated first and the important async caveat immediately after. Nothing is redundant with the title or annotations.

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?

An output schema exists so return values need no explanation, and the annotations carry the safety profile; the description fills the one real gap (cancellation is a request, not a guarantee). Only minor gaps remain around job_id sourcing and behavior on invalid/non-owned IDs.

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 single job_id parameter has 0% schema description coverage, so the description must carry the meaning. It adds 'specific owned job', clarifying ownership scope, but says nothing about where to obtain the UUID or what happens if the ID is unknown or not owned.

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 and resource ('Request cancellation of a specific owned job') plus a scope qualifier ('owned'). It never names the adjacent tools (delete_job, cancel_operation), so the agent must infer the distinction, but the async 'request' framing already signals this is not an immediate deletion.

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?

Usage is implied by 'owned job' — the caller should only use it on jobs it owns — but there is no explicit when-to-use/when-not-to-use guidance and no mention of the sibling alternatives such as delete_job or cancel_operation. The agent is left to infer routing.

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