Question queries (AI Overview / featured snippet targets)

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

Annotations already indicate read-only and idempotent behavior. The description adds useful transparency by mentioning that it optionally fetches each page to inspect headings and FAQPage schema, making the extra network-facing behavior clear. No destructive side effects are implied.

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 three sentences, front-loads the main purpose, and uses examples efficiently. The final sentence about AI Overviews and answer engines is somewhat repetitive given the title, but it does not add significant bloat.

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 description covers purpose, optional behavior, and target use case, but because there is no output schema, it does not specify return fields or format beyond 'grouped by page'. It also does not mention limits or edge cases, though parameter descriptions cover date lag.

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 descriptions cover most parameters, including siteUrl, dates, and checkPages. However, top and minImpressions lack descriptions, and the description text does not clarify those two parameters. The parameter names are reasonably self-explanatory but not fully documented.

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?

Clearly states the verb 'Find' and the specific resource: question-style queries with impressions, grouped by page. It also gives the use context (AI Overviews and featured snippet targets) and includes concrete query examples, making its purpose distinct from general search analytics tools.

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 when to use the tool by mentioning AI Overviews and answer engines, and it notes optional page-level checking. However, it does not explicitly contrast with sibling tools like gsc_search_analytics or keyword_suggest, nor does it state when not to use this tool.

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