delete_job

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

With no annotations provided, the description must disclose behavioral traits. It states the action and return format, but it does not mention that deletion is irreversible, whether permissions are needed, or what happens if the job is not in a queued/running state. This is a mutation tool, so more safety context is expected.

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?

The description is two short sentences: one for purpose and one for return format. It is front-loaded and contains no fluff, earning 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?

Although the tool is simple with one parameter, the description is incomplete: it does not explain the parameter's meaning, any required permissions, or edge cases (e.g., what happens if the job is already completed). The presence of an output schema reduces the need to describe returns, but the description still goes beyond that, yet misses critical operational context.

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 schema has zero description coverage for the single parameter job_id, and the description does not explain what job_id refers to or how to obtain it. The return message mentions 'job_id' but not its meaning as input. The description fails to compensate for the schema's lack of parameter documentation.

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 clearly states the tool's action: 'Delete (cancel) a queued or running job.' This is a specific verb and resource, and it distinguishes this tool from siblings like submit_job, list_jobs, and get_job_status.

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 tool versus alternatives, nor any mention of exclusions or prerequisites. The phrase 'queued or running' implies it is for active jobs, but it does not explicitly say when not to use it or point to alternative tools.

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