gsc_get_performance_overview

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

No annotations are provided, so the description carries full burden. It describes output as totals and daily breakdown, and implies a read-only operation. It does not mention auth or error handling, but given the simplicity, it is adequately transparent.

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 concise paragraphs: first clearly states purpose and usage, second documents parameters. Every sentence adds value, and information is front-loaded.

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 fully explains return values (totals and daily breakdown). Also mentions dependency on gsc_list_properties for obtaining the site_url. No gaps for the tool's scope.

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 0%, so description must compensate. It explains site_url format precisely, referencing gsc_list_properties, and notes the default for days. Both parameters are well-described.

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 provides an executive summary with daily trends for clicks, impressions, CTR, and average position, plus a day-by-day breakdown. It distinguishes itself from the sibling tool gsc_get_search_analytics by noting that the latter is for detailed query-level data.

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?

Explicitly states when to use: quick snapshots, dashboards, spotting traffic spikes or drops. Also provides a clear alternative: for detailed query-level data, use gsc_get_search_analytics.

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