nws_app_cancel_import

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait — the cancellation makes no remote changes — which is precisely the kind of context structured fields do not provide. However, it omits what happens to the pending confirmation record, whether auth is required, idempotency, and error behavior for an already-committed or expired confirmation.

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 resource and the scope front-loaded and the side-effect qualifier trailing. Nothing is padded and every clause carries information.

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 described, and the tool is a simple single-parameter mutation. The description covers action, scope, and the absence of remote side effects. What remains thin is lifecycle detail (state of the confirmation after cancel, failure modes) against a tool with no annotation coverage.

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 single parameter has 0% schema description coverage, so the description must compensate. It partially does: 'one pending NWP import confirmation' tells the agent the confirmation_id must reference a still-pending confirmation, not a completed one. It adds no format, source, or retrieval guidance (e.g., where to obtain the ID).

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'), a specific resource ('one pending NWP import confirmation'), and a scope ('one'). This is clearly distinct in intent from nws_app_commit_import and nws_app_preview_import, though it never names those siblings to confirm the routing.

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 the precondition that a confirmation must not yet be committed, and 'without remote changes' contrasts implicitly with commit. But there is no explicit 'use this when…' or 'do not use if the import was already committed' guidance, and no sibling is named.

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