finance_reports__list

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

Annotations already mark this as read-only and idempotent, and the description adds valuable context: gzipped TSV format, auth requirements, and the difference between raw blob and parsed rows. No contradictions with annotations; the added context goes beyond the structured hints.

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 short sentences: action/format, requirements, and parse behavior. Front-loaded and every sentence earns its place. No unnecessary words or redundancy.

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?

Given the rich parameter schema and annotations, the description covers the core behavior, auth, and output format. It doesn't explain pagination or full return structure, but those are already in the parse and max_rows schema descriptions. Sufficient for an agent to effectively select and invoke the 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 parameter semantics are already fully documented. The description only mentions parse=true, which the schema explains in more detail (base64, headers/rows/totalRows/truncated). It adds no new parameter meaning beyond the schema, so 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 tool downloads a finance report as gzipped TSV, which is a specific verb+resource+format. It also names the endpoint, making the operation unambiguous. It distinguishes from sibling tools like sales_reports__list by resource type.

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 gives clear context on when to use: requires ASC_VENDOR_NUMBER and a Finance role, and explains the parse option for decoded output. It does not explicitly mention alternatives or exclusions, but the prerequisites and behavior provide solid guidance.

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