nws_cancel_duty_auto_assign

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

With no annotations, the description does disclose the most important trait: no remote changes are made, so this is a safe local cleanup. It omits other behavior an agent may need – whether the call is idempotent, what happens with an invalid or expired confirmation_id, and how the confirmation_id lifecycle works.

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?

A single tight sentence with zero filler; the key scope constraint ('pending ... preview', 'without remote changes') is front-loaded.

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?

An output schema exists, so return values need not be explained. However, with no annotations and an undocumented parameter, the description should have stated where confirmation_id comes from and whether the preview is discarded permanently; that prerequisite context is missing.

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 sole parameter, confirmation_id, has 0% schema description coverage and is never mentioned in the description. The description does not explain that the ID must come from the preview tool or what form it takes, leaving the parameter's semantics to inference from the name alone.

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?

States a precise verb+resource: cancel a pending duty auto-assignment preview. The phrase 'without remote changes' distinguishes it from the commit sibling (nws_commit_duty_auto_assign) and makes clear it is the discard step of the preview/commit/cancel triplet.

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?

Implied usage only: an agent can infer it is used to discard a preview created by nws_preview_duty_auto_assign. It does not explicitly name the preview/commit alternatives or state preconditions, so guidance is implicit rather than explicit.

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