get_analytics_report_data

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

No annotations are provided, so the description should disclose behavioral traits. It states the tool gets data but does not mention whether it is read-only, if authentication is required, what the response structure is (e.g., pagination, size limits), or if there are performance implications. The examples hint at columns but are insufficient.

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 a single, front-loaded sentence that efficiently conveys the core purpose and provides examples. No redundant wording or irrelevant details.

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 lack of an output schema, the description should fully describe the return value. It lists a few example data fields but omits structural details, pagination, or limitations. Also, no usage guidance is provided, making the description incomplete for a tool with 3 parameters.

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?

Parameter descriptions in the schema already cover the meaning (reportId, granularity, instanceLimit). The overall description adds context about the type of data returned, but does not enhance parameter-specific semantics beyond the schema. With 100% schema coverage, the baseline of 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 retrieves actual data (row data) of a specified report, listing specific examples like search impressions and page views. It differentiates from siblings like list_analytics_reports (which lists reports) and get_sales_report (which likely returns summary data), but could be more explicit about the exact type of data.

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 no guidance on when to use this tool versus alternatives such as get_sales_report or list_analytics_reports. The schema parameter description for reportId mentions it comes from list_analytics_reports, but the main description lacks any usage context or prerequisites.

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