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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds one behavioral trait: data is delayed by 2-3 days, which is useful. However, it does not disclose other behaviors like pagination, rate limits, aggregation effects, or how the data_state parameter affects results. With annotations covering the read-only nature, the description adds some but not rich context.

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 extremely concise: two short sentences, with the core purpose front-loaded and the delay note appended. Every word earns its place. There is no fluff or repetition, and it is easy to parse quickly.

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 tool with 10 parameters (4 required), no output schema, and only 10% schema description coverage. The description does not explain how to construct valid queries, what the dimensions and filters options mean, the significance of aggregation_type, or the meaning of data_state. It also lacks information about response format or pagination behavior. For an agent to use this correctly, it would need substantial external knowledge. The description is severely inadequate.

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 10% (only site_url has a description). The description mentions the metrics returned (clicks, impressions, CTR, average position), which indirectly hints at what the tool returns, but it does not explain how parameters like dimensions, filters, aggregation_type, or data_state work. The schema has enums but no descriptions for most properties, and the description does not compensate for this gap. It adds minimal semantic value 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 clearly states the tool queries Google Search Console Search Analytics for clicks, impressions, CTR, and average position. It names the resource (GSC Search Analytics) and the specific metrics, distinguishing it from generic tools. However, it does not explicitly differentiate it from sibling tools like get_gsc_top_queries or get_gsc_top_pages, which are more specialized, so it doesn't fully clarify when this general query tool is preferred.

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 no guidance on when to use this tool versus alternatives such as get_gsc_top_queries, get_gsc_top_pages, or get_gsc_page_queries. It does not mention any exclusions or conditions that would route an agent to a different tool. The only contextual note is the data delay, but that is about data freshness, not usage selection.

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