download_document

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

With no annotations provided, the description must carry the full behavioral burden, but it only states the action and destination. It does not disclose side effects, file overwrite behavior, directory creation, authentication requirements, or failure modes.

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 concise, front-loaded with the main action, and the parameter notes are formatted clearly without redundancy. Every line adds useful 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?

For a simple download tool, the description covers the essential parameters and destination behavior, but it lacks usage guidance, return/output expectations, and behavioral notes beyond the basic action. It is adequate for straightforward invocation but leaves gaps for an agent navigating sibling tools.

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 has 0% description coverage, so the description compensates by explaining 'original' as the choice between original upload and archived PDF, and 'save_as' as a full path defaulting to PAPERLESS_DOWNLOAD_DIR. document_id is not described, but its meaning is self-evident.

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 action as 'Download document file to local disk' with a specific verb and resource, making the core purpose obvious. It doesn't explicitly differentiate from the sibling 'get_document', but the download-to-disk framing is distinct enough.

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 provides no guidance on when to use this tool versus alternatives like get_document or search_documents. It states what the tool does but offers no context about which scenarios call for it.

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