nws_app_cancel_publish

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 add one genuinely useful behavioral fact: the cancellation happens 'without remote changes', i.e. it is a local discard with no remote side effects. It says nothing about idempotency, what happens to an invalid/expired confirmation_id, or whether the confirmation becomes unusable, which is a real gap for a state-changing tool with zero annotation coverage.

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 the action front-loaded and zero filler. Nothing could be removed without losing meaning.

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 no explanation, and there is only one required parameter. What is missing is the origin of the confirmation_id and the behavior on invalid input; otherwise the definition is sufficient to call the tool.

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 0%, so the single required parameter 'confirmation_id' is undocumented in the schema. The description only implies that the id refers to a pending publish confirmation; it does not say how the id is obtained or what format it takes. That is partial compensation for a low-coverage 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?

States a specific verb ('Cancel') and a specific resource ('one pending NWP publish confirmation'), which sets it apart from the preview/commit publish siblings. It stops short of naming those siblings as the alternative path, so differentiation is inferred rather than stated.

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 word 'pending' implies this only applies to a confirmation that has been previewed but not committed, which is useful implied guidance. There is no explicit when-to-use, no statement of what to do if the confirmation is already committed or expired, and no named alternative (e.g. nws_app_commit_publish).

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