gsc_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 for behavioral disclosure. It mentions return metrics and grouping options, but omits important behaviors such as pagination (rowLimit/startRow), data freshness (dataState), filtering behavior, sampling, or rate limits. This is a notable gap for an API with these capabilities.

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. It is concise and directly conveys the essential function and key return values without unnecessary fluff.

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?

This is a complex 9-parameter tool with no output schema and no annotations. The description covers only the basics (metrics and dimensions) but omits return structure details, pagination behavior, filter usage, and data freshness considerations. For a tool of this complexity, the description is insufficient to fully prepare an agent for correct usage.

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 100%, so all 9 parameters are already documented in the schema. The description adds a general statement about breakdown dimensions ('query, page, country, device, or date') which merely echoes the dimensions enum, providing no additional parameter-level meaning beyond the 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 uses a specific verb ('Query') and resource ('Google Search Console search analytics data'), and further specifies the metrics returned and grouping dimensions. This clearly distinguishes it from sibling tools like gsc_top_queries and gsc_top_pages, which are likely specialized subsets.

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 clearly states the tool queries search analytics data, which is the primary use case, but provides no explicit guidance on when to use alternatives like gsc_top_queries or gsc_top_pages. No exclusions or comparisons are mentioned, leaving the choice implicit.

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