job_cancel

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description reveals nothing about side effects, idempotency, required permissions, or what happens after cancellation. No behavioral information is disclosed.

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 words, but this is under-specification, not conciseness. There is no information to structure or front-load. It fails to provide even minimal useful 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?

With 13 parameters, 2 required, no annotations, and no output schema, the description is completely inadequate. An agent cannot determine how to correctly invoke this tool or interpret its behavior. The description is essentially non-existent.

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 description offers no explanation of any of the 13 parameters. Required fields like context and operation_id are completely undocumented, as are enums like action. The description adds zero semantic value beyond the raw schema.

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 is 'job cancel', which simply restates the tool name. It provides no verb-resource specificity and does nothing to distinguish it from siblings like job_resume or status. This is a pure tautology.

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?

No guidance on when to use this tool versus alternatives. It does not mention any context, conditions, or exclusions. An agent would have no idea when to invoke job_cancel over job_resume or job.

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