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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description merely repeats 'Delete a job' and adds no extra behavioral context such as irreversibility, cascade effects, permission requirements, or whether deletion can be undone. It does not contradict the annotations but contributes no additional transparency.

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 one sentence with no wasted words and the action is front-loaded. It is appropriately terse for a single-parameter delete tool, though it sacrifices informative detail for brevity.

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 tool with no output schema, the description is minimally acceptable but lacks details about deletion semantics such as permanence, side effects, or success response. The annotations and complete parameter schema make the tool callable, but the description alone leaves some contextual gaps.

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 100%, and the id parameter is already documented as 'Job id or alias.' The tool description adds no additional parameter semantics beyond targeting a job by id. With high schema coverage, the baseline score of 3 is appropriate.

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 states a clear action verb and resource: 'Delete a job.' This distinguishes it from sibling delete_* tools because the resource is named. However, it essentially restates the tool name and title without adding any scope or nuance, so it does not reach a 5.

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 about when to delete a job versus alternatives like updating it, closing it, setting its status, or other lifecycle operations. No conditions, exclusions, or sibling comparisons are provided. The agent must infer usage solely from the tool name.

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