get_gsc_summary

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

No annotations are provided, so the description bears the full burden. It mentions 'over a window' but does not specify the default window, how the window is set, or any constraints like rate limits, data freshness, or that it is read-only. Minimal disclosure beyond purpose.

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, direct sentence that front-loads the key information without extraneous words.

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?

Given zero parameters, no output schema, and no annotations, the description leaves critical usage details unknown (e.g., required property context, date range format, output structure). It is insufficient for an AI agent to invoke correctly without additional context.

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?

The input schema defines zero parameters (with additionalProperties true), yet the description implies a date window must be specified. This adds meaning but lacks clarity on how to specify the window—contradicting the schema's apparent lack of needed parameters.

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 returns GSC metrics (clicks, impressions, CTR, position) with a branded vs non-branded breakdown. This distinguishes it from sibling tools focused on GA4 data or specific keywords/pages.

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 implies it should be used for Google Search Console performance data vs GA4 tools, but does not explicitly state when to use or not use it, nor mention any prerequisites like a configured property.

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