fetch_analytics_report

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral detail beyond those annotations: it resolves the request, looks up the report by name, selects the latest instance unless overridden, and downloads all segments. This gives the agent an accurate mental model of the operation's internal flow.

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 compact and well-structured: a one-sentence summary of the full pipeline, followed by a two-sentence elaboration of the steps and the prerequisite. Every sentence contributes information, and the most important context is front-loaded.

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 a complex tool with 7 parameters and an output schema, the description covers the essential workflow: request resolution, report lookup, instance selection, segment download, and the list_reports prerequisite. Remaining parameter details are fully documented in the schema, and return values are covered by the output schema, so nothing critical is missing.

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 the baseline is 3. The description adds value beyond the schema by explaining semantic relationships: report_name must be exact and can come from list_reports, while processing_date defaults to the latest instance unless provided. This helps the agent choose and populate the right parameters.

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 opens with a specific verb and resource: 'Fetch one analytics report end to end: request, report, instance, rows.' It clearly names the pipeline of objects involved and distinguishes this from the sibling list_* and download_* tools by framing it as an end-to-end fetch.

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 and a concrete prerequisite: 'Call list_reports first if you do not know the exact report name.' It also explains the default instance-selection behavior. However, it does not explicitly state when to prefer this tool over closely related siblings like download_report_instance.

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