nws_restore_cancel

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

No annotations are provided, so the description carries the full burden. It does disclose one important behavioral trait: the operation writes no remote data. However, it leaves much unsaid, including whether the preview state is discarded or expires, whether the cancellation is reversible, what permissions are needed, and what happens if the confirmation_id is stale or unknown.

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?

The description is a single front-loaded clause with zero waste: the action and the safety-relevant constraint appear together. For a one-parameter cancel tool, this length is appropriate.

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 the description need not explain return values, and the tool's surface is small. Even so, the description omits the essential workflow context: the tool's role in the preview and commit/cancel triad and the origin and meaning of confirmation_id. These omissions still leave an agent unsure how to call the tool correctly.

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, so the schema documents nothing about it. The description does not say what a confirmation_id is, where an agent obtains it (presumably from nws_restore_preview), or whether it is scoped or expires. With such low schema coverage, the description should have compensated for this gap but does not.

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 states a specific verb ("Cancel") and a specific resource ("a pending backup restore preview"), so an agent can tell it apart from nws_restore_preview and nws_restore_commit, which create or apply a restore. It does not name those sibling tools explicitly, so the differentiation is implicit rather than spelled out.

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?

Saying the tool cancels a "pending backup restore preview" implies that it is used after nws_restore_preview and instead of nws_restore_commit, but the description never states this sequence, never states a prerequisite such as requiring an active preview before it can be cancelled, and never says when not to use it.

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