cancel_queued_build

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

Annotation idempotentHint is false, but description claims the tool is idempotent. This is a direct contradiction. The description does disclose the 404 return condition, but the contradiction undermines trust.

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?

Two sentences with no wasted words. Every sentence adds value: purpose, scope, idempotency, and error condition.

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?

The description explains the return behavior (404) for edge cases, which compensates for the lack of output schema. It could mention the success response, but overall it is sufficient for a simple cancel operation.

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 100% and the parameter buildId is described as 'Queued build ID'. The description does not add any additional semantic meaning beyond the schema, which is adequate.

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 specifies 'Cancel a queued (not-yet-running) build' with a clear verb and resource, distinguishing it from sibling tools like cancel_build. It also notes idempotency and the 404 response for already-started/cancelled builds.

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 explicitly states this tool is for 'queued (not-yet-running)' builds and clarifies behavior when build has started or was cancelled. It implies not to use for running builds, but does not explicitly name the alternative (cancel_build).

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