rhino_render_queue_cancel

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

readOnlyHint=false already signals mutation, and the description adds that the tool acts on running or queued jobs. However, it does not disclose consequences such as irreversibility, whether a running render is aborted immediately, or what happens to any partial output.

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 eight-word sentence that front-loads the action and object. There is no filler, and every word 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 one-parameter cancellation tool with an output schema and a well-described job_id, the definition is nearly complete. A brief note on idempotency or irreversibility would improve it, but an agent can correctly invoke it with the current information.

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 tool description itself adds no parameter guidance, but the input schema's nested job_id description ('GUID returned by rhino_render_queue_submit') provides strong provenance. The schema carries the semantic weight, so the description does not need to 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?

The description uses a specific verb, 'Cancel', with a clear resource, 'a running or queued render job'. This unambiguously differentiates it from sibling tools like rhino_render_queue_submit, rhino_render_queue_status, and rhino_render_queue_list.

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?

The description specifies the eligible job states ('running or queued'), giving an agent clear context for when the tool applies. It does not name exclusions or alternative tools, but the operation is distinct enough among the render-queue siblings.

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