query_analytics

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

No annotations provided, and description does not disclose read-only nature, rate limits, or side effects. Minimal transparency for a data query tool.

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?

Single sentence that clearly communicates the tool's function. Efficient and to the point, though it lacks any structure beyond one line.

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?

No output schema, no annotations, and no behavioral context. For a GA4 query tool with 5 parameters, more detail on return values and query limits is expected.

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 covers all 5 parameters with descriptions, but propertyId description is an example ('325253028') rather than a semantic explanation. The description adds 'custom dimensions, metrics, and date ranges' which reinforces schema but does not add new meaning.

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?

Description states it queries Google Analytics 4 data with custom dimensions, metrics, and date ranges, which is clear. However, it does not differentiate from siblings like get_conversion_data, but the verb 'query' and mention of 'custom' imply flexibility.

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?

No guidance on when to use this vs alternatives like get_custom_report or get_traffic_sources. Missing context such as prerequisites or authorization requirements.

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