analytics_report_instances__get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds no behavioral traits beyond the read operation itself. It does not mention response size, authentication, or any limitations. No contradiction, but the description contributes no meaningful transparency 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 extremely concise with two short sentences, starting with the action and including the endpoint. No unnecessary words or repetition.

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 simple read-by-ID operation, the description, schema, and annotations are sufficient. The lack of an output schema is mitigated by the clear purpose and parameter documentation. A minor gap is no explicit mention of when to use this tool versus list operations, but overall context is adequate.

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?

The schema descriptions provide complete coverage for both parameters, including the enum values and size warning for fields_analyticsReportInstances. The tool description itself does not add parameter explanation, so a baseline score of 3 is appropriate given full schema coverage.

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 uses a specific verb 'Read' with a clear resource ('analytics report instance') and scope ('by ID'), which distinguishes it from list operations and sibling tools like analytics_reports__instances__list. The HTTP endpoint further specifies the exact operation.

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?

Usage context is implied via 'by ID' and the schema's 'ID from the matching list call', but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions. No direct reference to sibling tools is provided.

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