job.cancel

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

Annotations already supply readOnlyHint, idempotentHint, and destructiveHint, and the description's 'Risk: read' aligns with them. It adds mild context with maturity L3 and per-request policy checks, but it does not describe what cancelling actually does to a job or whether it is reversible.

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 short and front-loaded, with no redundant prose. However, its first sentence is largely a restatement of the tool name and the second is generic policy text, so brevity is achieved at the expense of substantive content.

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 cancellation operation, the description omits the core behavior, effect on the target job, and when cancellation is appropriate. The output schema and annotations mitigate some gaps, but the description alone is not sufficient for an agent to confidently invoke the tool.

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 coverage is 60%, so the description should compensate for the remaining parameter semantics, but it does not. It only mentions generic 'argument checks' and adds no meaning for jobId or the other parameters beyond what the schema already states.

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 only restates the command name as 'PartMe Blender Harness command `job.cancel`' without explaining what the operation does. An agent must infer from the tool name that it cancels a job, and the description does not differentiate it from sibling job tools such as job_submit, job_status, job_resume, or job_recover.

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 call this tool versus its siblings or what conditions warrant cancelling a job. The mention of 'requirements' is generic policy boilerplate, not actionable usage direction.

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