download_finance_report

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

With no annotations, the description only discloses the output format (CSV, decompressed from gzip). It does not mention side effects, authorization needs, rate limits, or error behavior. This is insufficient for an agent to understand the tool's behavior.

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 very concise with one sentence, but it contains an inaccuracy. While short, the misinformation detracts from its value.

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?

The description explains the output format (CSV, decompressed from gzip) but does not detail the CSV structure or fields. Given no output schema, more context on the return value would be helpful. The required parameter inaccuracy also reduces completeness.

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%, so baseline is 3. The description adds a misleading statement about required parameters (vendor_number is not required) and does not add any new meaning beyond the schema for the other parameters. It actually degrades understanding.

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 states it downloads a financial report as CSV text, which is clear. However, it incorrectly states that a vendor number is required, which contradicts the schema where only report_date and region_code are required. This misstatement reduces clarity.

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 like download_sales_report. The description does not provide any context for choosing this tool over siblings.

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