sales_reports__list

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

Annotations already indicate read-only and idempotent. The description adds that the tool downloads gzipped TSV files via GET, requires specific credentials, and is nondestructive. This provides useful behavioral context beyond annotations.

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 two sentences with no fluff: first states action and output, second covers requirements and HTTP method. Information is front-loaded and efficiently communicated.

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 7 parameters and no output schema, the description explains the output format and auth requirements. It omits pagination details (next_url), but schema covers that. Overall, it provides sufficient context for an experienced user.

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 descriptions already define each parameter. The tool description adds minimal parameter insight, only contextualizing that the filters relate to sales/subscription reports. This is adequate but not exceptional.

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 verb 'Download', the resource 'sales or subscription report', and the format 'gzipped TSV'. It distinguishes from siblings like 'finance_reports__list' by specifying the report type and download format.

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 mentions prerequisites (vendor number, role) and HTTP method, implying usage context. However, it does not explicitly guide when to use this tool vs alternatives like 'finance_reports__list' or 'analytics_reports__get'.

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