get_search_analytics

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

With no annotations, the description carries the burden. It discloses that domain properties cover all subdomains and how to analyze a specific subdomain, plus row_limit boundaries. It stops short of explicitly stating read-only behavior or error handling, but the output schema covers return values.

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 'Args:' block is well-structured and informative, but slightly verbose with examples and recommendations. Every sentence contributes value, so it earns a high score, though it could be trimmed marginally.

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?

An output schema exists, so return values are covered. The description covers all four parameters, provides practical guidance, and points to an alternative tool for advanced needs. It is complete for a tool of this complexity.

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%, and the description thoroughly compensates by explaining each parameter: site_url format with examples, days default, dimensions accepted values and comma-separated usage, and row_limit recommendations including thresholds for different use cases.

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 uses a specific verb and resource: 'Get search analytics data for a specific property.' It clearly distinguishes itself from the sibling tool get_advanced_search_analytics by mentioning row limits and directing bulk exports to that tool.

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?

Explicitly states when to use get_advanced_search_analytics (for bulk exports beyond 500 rows) and provides detailed guidance on handling domain vs. site properties, including filtering by page. This clarifies appropriate usage vs. alternatives.

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