gsc_search_performance

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

With no annotations, the description carries the full burden and falls short: it says nothing about authentication/verified-property requirements, rate limits, how the dimension choice changes aggregation, or whether the default limit caps results at 1000 rows. Only the phrase 'Google Search Console' hints at the data source.

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 listing metrics first and breakdowns second, with no filler. It is efficient, though the fragmentary noun-phrase style leaves the action verb implicit.

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?

With no output schema, the description must convey return shape; it does name the metrics, which is helpful, but omits pagination/limit behavior, date-range semantics, and auth requirements. It is minimally adequate rather than complete for a 5-parameter analytics 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 60%, and the description restates the dimension values (date, query, page, country, device) that the enum already lists, adding little beyond the schema. It offers no guidance on the 1000-row limit or the interaction between dimension and returned 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?

It names the specific resource (Google Search Console performance data) and enumerates the metrics returned (clicks, impressions, CTR, position) plus the available breakdowns, so an agent knows what data it yields. It does not, however, distinguish itself from close siblings like gsc_page_performance or gsc_query_advanced, which appear to overlap.

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?

There is no when-to-use guidance, no mention of prerequisites (a verified property is required), and no routing to alternatives such as gsc_page_performance or gsc_query_advanced. The only hint of context is the enumeration of dimensions, which the enum already supplies.

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