get_search_analytics

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

With no annotations, the description carries the full burden. It discloses key behaviors: domain property coverage, default values, dimension options, and row_limit semantics. It doesn't mention auth/rate limits, but for a data retrieval tool with output schema present, this is adequate. Slight deduction for not stating the return format explicitly.

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 well-structured with an Args section, front-loaded main purpose, and every sentence adds value. It is longer than minimal but efficiently packed with essential guidance without fluff.

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 tool has an output schema, the description needn't explain return values. It covers all parameters with practical advice and alternative tool mention, making it complete for a moderately complex tool. No gaps in coverage.

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 coverage is 0%, so the description fully compensates. It explains site_url with examples and scale (domain vs. page), days default, dimensions allowed values and multiple dimensions, and row_limit with recommended ranges. This adds significant meaning beyond the raw schema.

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 clearly states the tool's function: 'Get search analytics data for a specific property.' It uses a specific verb (Get), identifies the resource (search analytics data), and distinguishes it from the sibling get_advanced_search_analytics by noting pagination support for bulk exports.

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?

Explicit guidance is provided: dimensions and row_limit usage recommendations, plus a direct alternative: 'For bulk exports beyond 500 rows, use get_advanced_search_analytics which supports pagination.' This clearly indicates when to use this tool vs. the alternative.

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