search.queries

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

Annotations already declare readOnlyHint=true, ensuring safety. The description adds useful behavioral context: data lags ~2 days, synced daily, and requires a connected Search Console property (returns empty list if none). This goes beyond what annotations provide.

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?

Well-structured, front-loaded with core definition, then use cases, examples, and limitations. Every sentence adds value, no fluff.

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 the presence of an output schema (not shown but exists), return values are covered. The description covers purpose, limitations, prerequisites, and alternatives to other tools. Complete for the complexity.

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?

Input schema has 100% description coverage, but the description adds practical usage context (e.g., period examples, hint to call projects.list for project_id, default limit). This adds value beyond the schema.

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 Google Search Console query metrics (clicks, impressions, CTR, position) for search terms that drove clicks. It explicitly distinguishes from sibling tool 'search.landing_pages' by noting that the latter covers post-click activity.

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?

Provides explicit when-to-use examples ('what are we ranking for', 'which queries drive the most clicks', 'where do we sit on [term]') and includes limitations (only queries with at least one click, no zero-click impressions). Also directs to a sibling tool for post-click data.

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