Download item file

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

With no annotations, description fully carries burden. Discloses that JSON responses are returned directly, binary requires savePath, and binary contents are never streamed into conversation. Adds critical behavioral context beyond basic purpose.

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?

Three tightly written sentences: first states purpose, next two detail behavior. Front-loaded, no irrelevant details.

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 download tool with 5 parameters and no output schema, description explains when parameters are needed and what outputs to expect. Lacks mention of error conditions (e.g., invalid IDs), but covers core usage.

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 already covers 100% of parameters with descriptions. Description adds value by clarifying that savePath is required for binary responses and explaining the output handling for both cases.

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?

Clearly states 'Download a file attached to an item' and distinguishes behavior between JSON and binary responses. Specifically distinguishes from sibling tools like get_item_file and upload_item_file.

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?

Describes when to use (to download file) and provides context on JSON vs binary responses. Does not explicitly mention when not to use, but implied by sibling set.

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