Get Analytics Report Data

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

The description fully discloses behavior beyond annotations: it downloads and decompresses segments, returns a preview with max 50 rows, includes a truncated flag, and explains error conditions. Annotations declare readOnlyHint, idempotentHint, etc., and the description adds rich context without contradiction.

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 well-structured with clear sections (Args, Returns, Error Handling) and is front-loaded with the main purpose. While not overly verbose, it contains detailed return fields and error info; minor redundancy exists (e.g., repeating schema descriptions), but it remains efficient.

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 is fully self-contained for a complex tool: it explains the entire fetch process, return structure (including truncation and row limits), and error scenarios. No output schema exists, so the description must supply this, which it does comprehensively.

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% with descriptions, so baseline is 3. The description adds value by explaining the default for granularity, the role of processingDate (latest instance if omitted), and the relationship to asc_list_analytics_reports, thus exceeding the schema alone.

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 'Fetch the data of an analytics report' and details the process (resolves instance, downloads, decompresses, returns preview). It distinguishes from siblings by focusing on data retrieval after reporting, contrasting with asc_list_analytics_reports which lists report IDs, and asc_request_analytics_reports which creates requests.

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 clear prerequisites (reportId from asc_list_analytics_reports) and optional granularity/processingDate. It includes error handling context (report may take up to 48 hours). However, it does not explicitly mention when not to use this tool versus alternatives like asc_get_sales_report, so it lacks a clear exclusionary note.

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