spv_documents_download

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

The description discloses failure modes (SPV_FILE_PENDING, SPV_FILE_PURGED) which is useful, but it does not mention success behavior, side effects, permissions, or file overwriting. Without annotations, the burden is on the description, and it is only partially transparent.

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 two concise sentences, front-loaded with the core purpose. It includes failure modes without unnecessary detail, making it efficient and well-structured.

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 description provides the essential context: what the tool does, where it writes, and key failure scenarios. It does not elaborate on relationships with related tools or post-actions, but for a simple download operation, it is adequately complete.

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 schema covers all parameters with clear descriptions (uuid, companyId, outputPath). The description does not add extra context beyond the schema, so the baseline score of 3 applies.

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 the specific action (download), the resource (archived PDF of an SPV document), and the destination (local file). It also distinguishes the tool from siblings by focusing on the archived PDF and the download aspect.

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 description implies usage context by mentioning failure modes (SPV_FILE_PENDING, SPV_FILE_PURGED), which suggest preconditions (must fetch first, retention constraints). However, it does not explicitly compare with related tools like spv_documents_get, leaving some ambiguity about when to choose this over alternatives.

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