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

Annotations already declare destructiveHint=false and idempotentHint=true; the description reinforces this by stating it is a no-op on terminal renders, which is meaningful behavioral context beyond the annotation. It doesn't state permission or auth requirements, keeping it short of a 5.

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?

Three short sentences, front-loaded with the action and scope, then prerequisites, then the no-op caveat. No wasted words.

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?

No output schema exists, but for a simple 2-param cancellation the description covers the action, inputs, and terminal-state behavior, and annotations carry the safety profile. Only auth/permission context is missing.

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 100% and both parameters are documented in-schema, so the baseline is 3. The description adds only the provenance note that renderId comes from create_render, with no format or path syntax detail beyond the schema.

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?

Specific verb 'Cancel' on a specific resource 'in-flight render', with a parenthetical that scopes what counts (runaway/queued job). The name 'cancel_render' is clearly distinguished from siblings like cancel_compose, cancel_export, and cancel_job by resource.

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?

'Needs projectId + renderId (from create_render)' tells the agent the prerequisite producer of the identifiers, and 'No-op if already terminal' tells it when the call is pointless. It does not explicitly contrast with cancel_job or retry_render, but the resource-specific naming makes the routing clear.

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