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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context beyond them: caveats that qualify the figures, case-sensitive filter matching where all filters must hold, and the rule that bots are counted in pageviews alone. That is substantive disclosure for a read 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 purpose is front-loaded, but the body is one very long semicolon-chained sentence describing return fields. That detail is justified because there is no output schema, yet the run-on structure makes the definition harder to parse than the information requires.

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?

With 9 parameters, nested filter logic, and no output schema, the description carries the return contract itself (echoed inputs, totals, previous, change, per_day, basis, share, series granularity, and top breakdowns). It is close to complete, with the caveats left as a pointer to the response rather than enumerated.

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 domain, range, from/to, days/ending, filters, reason and bot. The description largely mirrors the schema (filters allowed dimensions, single-reason and single-bot narrowing, 'google is not Google'), adding only marginal meaning, which matches the baseline 3 for fully covered schemas.

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 opening sentence states a specific resource and scope: bot pageviews for a site over a range plus the prior period, and it explicitly differentiates itself from siblings ('no other tool's figures count them'). The dense, inverted phrasing makes the purpose slower to extract than it should be, but it is unambiguously stated.

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 is implied through references to get_site_summary for naming the site/range and for the caveats, and there is an instruction to read caveats before reporting. However, it never explicitly says when to choose this tool over get_site_summary or get_site_breakdown, only that its figures are the bot-specific ones.

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