cancel_job

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

With no annotations, the description carries the full burden, and it does disclose the meaningful behavioral trait that the entire process tree is terminated, not just the job. It stops short of stating irreversibility, required permissions, or confirmation/error behavior for an operation that is clearly destructive.

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?

One front-loaded sentence with no filler; the destructive scope detail is included and nothing is wasted.

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 destructive single-parameter tool with no annotations and no output schema, the description is adequate on intent but thin on consequences: it omits what success returns, how failures (unknown/already-complete job) are handled, and any permission requirements.

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% and the single job_id parameter is undocumented in both schema and description. The description does not say how to obtain a job_id, whether it accepts a name, or what form it takes, so it fails to compensate for the coverage gap.

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) plus resource (job), with the added scope that it terminates the complete process tree. No sibling is a competing cancel tool, so the agent can distinguish it cleanly from list_jobs/get_job_status/submit_job.

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?

"Queued or running" implies the tool is inapplicable to already-finished jobs, which is mild routing guidance. However, there is no explicit when-to-use vs when-not statement, no note about prerequisites or what happens if the job already completed.

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