Search Console: Top-Suchanfragen

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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety and external data source are already covered. The description adds that results are sorted by clicks and include specific metrics, which is useful context. However, it doesn't mention pagination limits, data freshness beyond what the schema says, or what happens if the property is invalid. With annotations covering the safety profile, a 3 is appropriate.

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?

One sentence, front-loaded with the core action, no wasted words. Efficient and clear.

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?

Covers the essential purpose and metrics. For a read-only analytics tool with fully documented parameters and annotations, it is nearly complete. It could mention that results are limited by default (25 rows) or how to interpret average position, but these are minor given the schema covers limits.

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 three parameters (tage, limit, property) are fully documented in the schema itself. The description adds no additional parameter meaning, such as timezone or date-range nuances. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb+resource: returns top search queries for a GSC property, listing the metrics (clicks, impressions, CTR, position) and the sort order. Clear for an agent. It doesn't explicitly distinguish itself from sibling gsc_seiten (likely top pages), but the 'Suchanfragen' (queries) focus is evident.

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?

Implied usage: query analytics data for a property. No explicit when-to-use or when-not-to-use guidance, and siblings like gsc_seiten (pages) are not referenced or contrasted. An agent must infer that this tool is for query-level data rather than page-level.

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