Render Cancel

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the agent knows repeats are safe and no data is destroyed. Beyond that the description adds nothing: it doesn't state what happens to a partially rendered file, whether the call errors when the job is already finished, or whether cancellation is synchronous.

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?

A single short sentence with zero filler and the action front-loaded. It is efficient, though at this length the brevity shades into under-specification.

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 one-parameter tool with no output schema and annotations covering idempotency/destructiveness, the description is minimally viable but omits caller-relevant details such as error conditions and the fact that job_id comes from render_start.

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?

One parameter exists with 0% schema description coverage, so the description carries the full burden but merely repeats 'job' without clarifying job_id format or where it comes from (presumably render_start). The schema is bare and the description does not compensate.

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 resource ('a running render job'), which is unambiguous and clearly distinct from siblings like render_start and render_status. However, it never names those siblings, so differentiation relies on the agent already knowing the render family.

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?

No explicit when-to-use or when-not guidance, and no reference to the obvious alternatives render_start/render_status. The agent must infer from the single sentence when cancellation is appropriate (e.g., only for in-flight jobs) with no help.

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