cancel_job_tool

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing beyond the one-line action. It does not state that cancellation is irreversible, whether in-progress work is stopped or merely flagged, permission requirements, or what happens to jobs that have already completed. For a state-mutating tool this is a substantial gap.

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 tight sentence with the action and object front-loaded and zero filler. It is appropriately sized, though its brevity is partly the cause of the missing behavioral detail rather than pure efficiency.

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 not be explained. However, for a destructive, unannotated mutation with one entirely undocumented parameter, the description omits the preconditions, irreversibility, and handle provenance an agent needs to invoke it safely.

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 0% for the single parameter 'job_handle', and the description adds nothing about its origin or format (e.g., where to obtain it from list_jobs_tool or a prior generate call). The parameter is documented only by its name.

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 gives a clear verb+resource ('Cancel a ... job') and even scopes it to queued or in-progress states, which is more specific than the bare tool name. It does not, however, name or differentiate itself from siblings such as delete_character_tool or list_jobs_tool, so the agent gets no explicit routing signal.

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?

There is no guidance on when to use this versus alternatives (e.g., list_jobs_tool to find the handle, get_status_tool to check state first). Nothing is said about whether already-completed jobs can be cancelled or what to do if the job is finished, leaving the agent to infer all preconditions.

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