nws_commit_attachment_upload

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses a mutation and an optimistic-concurrency condition ('if remote data is unchanged'), but omits permission requirements, what happens on conflict, reversibility, and how the upload is recorded.

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 front-loaded sentence with no wasted words. The action and the conditional guard are both stated efficiently.

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. But for a mutation tool with no annotations and an undocumented required confirmation_id, the description is only minimally complete: it states the action and staleness condition but not conflict handling or parameter provenance.

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% and the only required parameter, confirmation_id, is never explained. The word 'previewed' hints that confirmation_id may come from a preview, but the description does not state how to obtain or use it.

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 and resource: upload a previewed attachment and record it conditionally. This distinguishes it from preview/cancel siblings through the 'previewed' and 'record it if remote data is unchanged' wording, though it does not explicitly name an alternative tool.

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 phrase 'previewed attachment' implies the preview step must happen first, and 'if remote data is unchanged' gives a condition for use. However, it does not explicitly name the prerequisite tool, state when not to use it, or point to the cancel alternative.

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