nws_download_attachment

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

With no annotations, the description carries the full behavioral burden. It discloses that the file is 'owner-only,' which is useful, but it does not explain authentication, overwrite behavior for output_path, what sync_first does, error handling, or whether the download touches the remote system.

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 sentence with no wasted words. It is concise, though its brevity contributes to the under-specification seen in other dimensions.

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-value detail is not required. However, for a four-parameter tool with no annotations and 0% schema coverage, the description is far too sparse to guide correct invocation or explain sync_first and attachment selection.

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%, so the description must compensate for all four undocumented parameters. It loosely maps 'entity's attachment' to entity_type/identity and 'local file' to output_path, but does not explain sync_first, attachment selection, path format, or identity expectations.

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 gives a specific verb and resource: 'Download one entity's attachment' and adds that the result goes to an 'owner-only local file.' That distinguishes it from listing or uploading attachments, but it does not explicitly contrast with sibling tools like nws_list_attachments or nws_preview_attachment_upload.

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?

It implies the tool is used to download an attachment, but provides no explicit when-to-use guidance, no prerequisites, and no alternatives. The presence of nws_list_attachments and attachment upload/removal siblings makes the lack of routing guidance a real gap.

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