cancel_job

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the state-based restrictions (OPEN vs ASSIGNED) and the before-completion constraint, which are critical behavioral traits. It lacks details on consent direction and post-cancellation effects, but covers the most important rules.

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 a single concise sentence with a parenthetical for rules, containing no filler and front-loading the core action. Every word earns 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?

Given a single-parameter tool with no output schema, the description covers the essential state-based rules for cancellation. It lacks details about consent giver and post-cancellation consequences, but is largely sufficient for an agent to decide whether and how to invoke it.

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 description does not explicitly describe the jobId parameter, and schema description coverage is 0%. However, the parameter is self-evident from the tool name and action, and the rules imply the job must be in a cancelable state. It adds minimal value beyond the 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 clearly states the tool's action ('Cancel a job before completion') with a specific verb and resource, and the timing constraint. It distinguishes itself from sibling tools, as none of the siblings offer a cancellation operation.

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 rules 'only OPEN by poster; ASSIGNED requires consent' provide explicit conditions for when cancellation is permissible, effectively serving as when-to-use guidance. It does not name alternatives, but the eligibility criteria are clear enough to guide invocation.

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