download_official_statement

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

The description discloses key behaviors: downloading to local disk, resolving IssueView URLs to PDF links, and returning file path and size. Since no annotations are provided, the description carries full burden and does so adequately, though it omits error handling details.

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 extremely concise: two sentences that front-load the purpose and usage. Every sentence adds value with no redundancy or unnecessary detail.

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?

Despite lacking an output schema, the description states return values (file path + size). It covers input options and usage guidance comprehensively for a simple download tool.

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 coverage is 100%, so the schema already documents both parameters. The description adds minimal extra information beyond the schema (e.g., clarifying that IssueView URL is accepted). Baseline 3 is appropriate.

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 (download), the resource (Official Statement PDF from EMMA), and the destination (local disk). It also distinguishes from sibling tools like get_official_statement_pdf by focusing on downloading rather than retrieving a link.

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 a specific use case ('Use when the banker wants the OS to attach to a deck or read offline'), giving clear context for when to invoke this tool. It does not explicitly mention when not to use it or alternative tools, but the context is sufficient.

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