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

Annotations already flag destructiveHint=true, and the description adds specific behavioral details: if in progress, returns printer to rotation; no work recorded; schedule counters not reset. These go beyond the annotation's general destructive warning and help the agent understand consequences. It does not contradict any 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?

The description is two sentences, front-loaded with the core purpose and immediately clarifying the distinction from completing. Every clause adds value: the purpose, the printer rotation side effect, and the 'not the same' clarification. No wasted words.

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 simple one-parameter tool, the description covers the core behavior and side effects well. However, it omits details like when cancellation is valid (e.g., can a completed job be cancelled?), whether it can be undone, or how errors are surfaced. Given that there is no output schema and no parameter documentation, a bit more context would be expected, but the description is not severely lacking.

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 sole parameter job_id, and the description does not mention it at all. Since the parameter is undocumented in both schema and description, the description fails to compensate for the coverage gap. The agent is left to infer that job_id is the ID of the maintenance job, which is fairly obvious from the tool name, but there is no guidance on how to obtain it or any constraints.

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 action: cancel a maintenance job. It distinguishes this from completing it by noting that no work is recorded and counters are not reset, and it mentions the side effect of returning the printer to AutoPrint rotation. This differentiates it from sibling tools like complete_maintenance_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?

The description gives context on when to use it ('not going to happen') and explicitly contrasts with completing it. It implies the alternative (complete_maintenance_job) without naming it directly, and it does not explicitly state conditions under which cancellation is invalid (e.g., already completed). It provides enough guidance for an agent to choose between cancel and complete.

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