nws_cancel_attachment_change

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

With no annotations provided, the description carries the full burden. It does disclose the important behavior that cancellation results in no remote changes, but it omits permissions, idempotency, and what happens if the confirmation ID is stale or invalid.

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 compact sentence front-loads the action and resource with no wasted words. It is appropriately sized for a simple one-parameter cancellation tool.

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 output schema exists, so return values need not be explained. Still, for a tool requiring confirmation_id, the description should briefly connect that ID to the preview step and clarify whether cancellation requires a specific state.

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 only parameter, confirmation_id, has 0% schema description coverage, and the description never mentions it. An agent must infer that it comes from a prior preview/upload/removal step, but that relationship is not stated.

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 a specific verb and resource: cancel a pending attachment upload or removal. The phrase 'without remote changes' distinguishes it from commit-style sibling tools, though it does not explicitly name those alternatives.

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 is used after a preview and before a commit, and 'without remote changes' implies it abandons the change safely. However, it does not explicitly say when to use this versus nws_commit_attachment_upload, nws_commit_attachment_removal, or other cancel tools.

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