cancel_job

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

The annotation marks the tool as destructive, and the description adds that it 'kills its process group', indicating a forceful termination beyond a graceful cancel. This adds behavioral context not present in the annotation.

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, front-loaded sentence with no filler. 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 tool with one simple parameter, the description fully covers the action and its effect (killing the process group). No output schema is needed for a cancel operation, and the destructive nature is already annotated.

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?

With one job_id parameter and 0% schema description coverage, the description's phrase 'running job' implies that the job must be active, adding a semantic constraint. The parameter name is self-explanatory, and the description reinforces its meaning.

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 'running job', and adds the detail of killing its process group. This distinguishes it from siblings like get_job_status or list_jobs.

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 implies it is for stopping active jobs, but does not explicitly state when to use it over alternatives or mention any exclusions. No prerequisites or contrast with sibling tools are provided.

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