get_search_analytics

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

With no annotations, the description carries the transparency burden. It explains the exact URL format, domain/prefix distinction, grouped dimensions, and fallback to an advanced tool. It doesn't mention rate limits, data latency, or explicit read-only guarantees, but the 'Get' verb and detailed scoping provide solid behavioral context.

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 structured as an Args block with one line per parameter, each earning its place with concrete details. The first sentence states the purpose, and the rest is actionable parameter guidance with no filler.

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?

For a four-parameter tool with an output schema and no annotations, the description covers all necessary context: required property, optional parameters with defaults and valid values, recommended limits, and when to switch to a sibling tool. It is comprehensive and self-contained.

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%, but the descriptions fully compensate by detailing all four parameters: site_url format with examples, days default, dimensions options and comma-separated usage, and row_limit with recommended ranges and max. This adds meaning far 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 opens with 'Get search analytics data for a specific property,' which is a specific verb+resource statement. It clearly differentiates from sibling tools like list_properties and get_advanced_search_analytics by scoping to a property and noting when the advanced sibling should be used.

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?

Provides explicit usage guidance: exact site_url format from list_properties, domain property coverage, row_limit ranges for different use cases, and an explicit alternative for bulk exports ('For bulk exports beyond 500 rows, use get_advanced_search_analytics which supports pagination'). This is strong when-to-use and when-not-to-use guidance.

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