Query Search Analytics

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds a pagination behavior hint (startRow), which is genuinely useful, but reveals nothing about row caps, data freshness/state, rate limits, or result shape.

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?

Two tight sentences, front-loading the purpose before the pagination tip with no filler. Appropriately sized, though the second sentence carries little weight relative to the missing semantic detail.

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 10-parameter, nested-filter tool with no output schema and low schema description coverage, the description is too thin. It omits how dimensions drive the result granularity, the rowLimit ceiling of 25000, date format expectations, and filter group semantics that an agent would need to invoke it reliably.

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 only 30% across 10 parameters, so the description must compensate but does not. It explains startRow only, leaving siteUrl, dimensions, rowLimit, aggregationType, dataState and dimensionFilterGroups undocumented in prose; these are structured-only and potentially ambiguous, especially the nested filter group shape.

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?

States a specific verb (Query) and resource (Google Search Console Search Analytics) and enumerates the returned metrics (clicks, impressions, CTR, average position). It is clearly distinct from the sibling tools (sites, sitemaps, URL inspection), though it does not explicitly say so.

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 only usage guidance is 'Use startRow for pagination', which is a parameter tip rather than a when-to-use statement. There is no indication of when this should be chosen over alternatives or what preconditions (e.g., verified property) apply.

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