Query search analytics

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

With no annotations provided, the description carries the full burden. It discloses the output (clicks, impressions, CTR, position) and the core action (querying performance data). It does not mention rate limits, latency, destructive potential (though read-only is implied), or any error conditions. This is adequate but not thorough.

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 two sentences, front-loaded with the core purpose, and every sentence serves a clear function: stating what the tool does and guiding usage. No extraneous content.

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 10 parameters (0 required), 90% schema coverage, and no output schema, the description covers the essential use case. It briefly explains the output and mentions alternatives. It could benefit from mentioning pagination (startRow, rowLimit) or result format, but it is sufficient for a data query tool.

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 high (90%), so the baseline is 3. The tool description adds no additional parameter-specific information beyond what the schema already provides. It does not explain parameter interactions or provide examples.

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 it is 'the core Search Console performance query' that returns specific metrics (clicks, impressions, CTR, average position) broken down by requested dimensions over a date range. It also distinguishes from sibling tools by recommending 'top_queries / top_pages for quick cases.'

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 provides clear context on when to use this tool as the core query for detailed breakdowns and explicitly suggests alternatives ('top_queries / top_pages for quick cases'). However, it does not elaborate on when to avoid this tool or handle edge cases.

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