epost_download_all

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

No annotations are provided, so the description must carry the full burden. It only states the action and output but does not disclose behavioral traits such as whether it overwrites existing files, authentication requirements, rate limits, or error handling. This is insufficient for a bulk download operation.

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 sentence that immediately states the action and return value. It is front-loaded and contains no unnecessary words, making it efficient.

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 tool that downloads all letters, the description is too brief. It does not explain behavior on network failures, partial downloads, duplicate handling, or performance implications. No output schema exists to clarify the return value structure. Additional details are needed to ensure safe and effective use.

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 has no descriptions for the single parameter 'output_dir' (0% coverage). The description adds minimal meaning by mentioning 'to output_dir', but does not specify format, permissions, or how the directory is used. More detail is needed to compensate for the lack of schema descriptions.

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 tool downloads every letter from the letterbox to a specified directory and returns the saved paths. The verb 'Download' and resource 'every letter' are specific, and it distinguishes from sibling tools like 'epost_download_letter' that handle single letters.

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?

No guidance is given on when to use this tool versus alternatives (e.g., epost_download_letter), or any prerequisites or limitations. The description lacks context for appropriate usage.

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