get_search_analytics

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

With no annotations, the description carries the full disclosure burden. It covers defaults, the 500-row cap, allowed dimensions, comma-separated multi-dimensions, and the subdomain behavior of domain properties. It stops short of mentioning authorization or rate limits, but since this is a read-only analytics query, the most important behavioral constraints are disclosed.

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 definition is front-loaded with a one-sentence summary followed by a compact, scannable Args list. Each line adds meaningful guidance: defaults, options, max limits, and a pointer to the paginated sibling. No filler or redundancy is present.

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?

The description is complete for an agent to call this tool correctly: all parameters are explained, defaults are given, the 500-row boundary is explicit, and the paginated alternative is identified. An output schema exists, so documenting return values is unnecessary here.

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 0%, so the description must fully document the parameters—and it does. It explains site_url with exact GSC formats and subdomain filtering, days with a default, dimensions with allowed options and comma-separated examples, and row_limit with defaults, maximum, and suggested ranges. This exceeds what the schema provides.

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 clearly states the action and resource: 'Get search analytics data for a specific property.' It also distinguishes itself from get_advanced_search_analytics by noting that the advanced tool supports pagination for bulk exports, which prevents an agent from selecting the wrong sibling by mistake.

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 practical guidance for every parameter and explicitly states when to use an alternative: 'For bulk exports beyond 500 rows, use get_advanced_search_analytics which supports pagination.' It also explains how to choose site_url and row_limit ranges, giving an agent clear conditions for using this tool correctly.

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