nws_cancel_change

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

With no annotations, the description carries the full burden, and it does disclose one important trait: no remote data is written. However, it is silent on what happens to the confirmation_id (invalidated? reusable?), how it behaves if the preview was already committed or expired, and whether any local state is discarded.

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?

One sentence, verb-first, with the key safety property front-loaded and zero filler. Nothing is redundant or buried.

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 needn't be described, but for a cancel operation with a required, undocumented identifier and no annotations, the definition is thinner than ideal. The most important missing piece — the origin and lifecycle of confirmation_id — is absent.

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% for the single required parameter, so the description must compensate and does not — confirmation_id is never mentioned. An agent gets no hint that this ID comes from a prior preview call or what an invalid/expired ID produces.

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 specific verb (Cancel) and resource (a pending NWS change preview), and the phrase 'without writing remote data' clarifies the operation's nature. It is reasonably distinguishable from nws_commit_change and nws_preview_change, though it doesn't explicitly differentiate itself from similarly-named siblings like nws_public_speaker_cancel_change or nws_restore_cancel.

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?

Usage is only implied: an agent can infer this is called to abandon a preview rather than commit it, but the description never states when to use it versus nws_commit_change or how a preview comes into existence (presumably via nws_preview_change). No exclusions or prerequisites are given.

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