Download Attachment

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

With no annotations, the description fully discloses key behaviors: caching (subsequent calls return cached version), force re-download, return value (local file path). No hidden side effects or ambiguities remain.

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?

Front-loaded single-line purpose followed by three bullet points containing only essential behavioral details. No wasted words; perfectly scannable.

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 2-param tool with no output schema, the description covers purpose, constraints (stored attachments only), caching behavior, force parameter, and return value. References sibling clear_attachment_cache implicitly. No significant gaps.

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 100%, and itemKey already says 'get from get_item_children'. The description's mention of force=true adds no new semantics beyond the schema's 'Force re-download even if cached'. Baseline 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?

States exactly what it does: 'Download an attachment file (PDF, etc.) to local cache.' Specific verb (download) + resource (attachment file) + destination (local cache). Clearly distinguishes from all siblings, none of which handle attachment downloads.

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?

Provides usage conditions: 'Only works for stored attachments (imported_file, imported_url)' and explains caching behavior with force=true. Doesn't name alternative tools because no direct siblings exist, but the when-not-to-use guidance is explicit.

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