Query Search Analytics

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

No annotations are provided, so the description carries the full burden. It discloses that the tool queries performance data broken down by dimensions, but does not mention pagination behavior, data limits, authorization requirements, or response format. The schema adds some behavioral details, but the description itself is thin.

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?

A single, front-loaded sentence efficiently conveys the tool's purpose and key capabilities with no filler or repetition. It is appropriately sized for a query tool with a rich schema.

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?

Despite having 8 parameters and no output schema, the schema is very thorough, covering each parameter's meaning. The description is adequate for a read-oriented analytics query, but it does not mention return value shape or edge cases, which would have made it more complete.

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?

The schema has 100% coverage of parameters with descriptions, so the baseline is 3. The description adds little beyond restating the dimensions concept already present in the schema, mostly echoing 'query, page, country, device, or date' without providing additional semantic meaning.

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 queries Google Search Console performance data with specific metrics (clicks, impressions, CTR, position) and dimensions, distinguishing it from sibling tools that manage sites, sitemaps, or inspect URLs.

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 implies usage for performance data but does not explicitly state when to use this tool over alternatives, nor does it mention any exclusion conditions. Siblings are distinct enough that confusion is unlikely, but no direct guidance is provided.

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