analytics_advanced

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only lists metric categories and does not disclose whether this is a read-only operation, how date ranges interact with realtime metrics, or what the response format looks like. This is a significant gap for a data-querying 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?

The description is a single concise sentence with no wasted words. It efficiently communicates the tool's domain, though it could be more informative without sacrificing brevity. The structure is clean and front-loaded with the main subject.

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 absence of an output schema and annotations, and the presence of sibling analytics tools, the description is severely incomplete. It does not explain return values, date handling, or how this 'advanced' tool differs from analytics_query/analytics_compare. The agent is left without context to use it effectively.

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 description coverage is 100%, so the schema already documents all four parameters. The description adds limited value by listing metric types that partially map to the metricType enum, but it provides no extra detail on parameter combinations, constraints, or format beyond what the schema states.

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 lists metric categories (e-commerce, realtime, user behavior, conversion funnels) but lacks a verb like 'query' or 'retrieve'. It's not a tautology, but it's vague about the exact operation. It sets this tool apart from siblings by naming specific GA4 metric types, but the purpose remains unclear without an action.

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 is provided on when to use this tool over alternatives like analytics_query, analytics_compare, or analytics_anomalies. The description does not mention any exclusions, prerequisites, or trade-offs, leaving the agent without direction on selection.

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