gsc_search_analytics

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

With no annotations, the description carries full transparency responsibility. It does not state whether the operation is read-only, what permissions are required, how pagination works, or what the response structure looks like. It only mentions output metrics and dimensions, adding minimal behavioral context beyond the schema.

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 very short and efficient, with three sentences covering the main action, the return values, and the dimensions. Each sentence adds essential information without redundancy or filler, and the main verb 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?

The tool has 10 parameters, no output schema, and no annotations, yet the description is only a few sentences. It omits guidance on required parameters, pagination behavior, filtering capabilities, and response structure. The schema covers parameter semantics, but the description fails to provide the broader context needed for effective tool use.

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 parameters are individually documented. The description restates the dimension list but adds no extra meaning about parameter usage, formats, defaults, or interactions beyond what the schema already provides.

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 and lists the returned metrics (clicks, impressions, CTR, position) and available dimensions. This distinguishes it from sibling tools like gsc_list_sites and gsc_inspect_url, which handle site lists and URL inspection rather than analytics 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?

The description implies use for search analytics queries but does not explicitly state when to use it versus alternatives or provide exclusions. It does not reference any sibling tools or offer guidance on when this tool is preferred, so usage context is only implied.

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