ai_overview

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

The description discloses the use of SerpAPI, the free tier quota, and the need to set SERPAPI_KEY. It also notes that location affects eligibility. Without annotations, this covers key behavioral aspects, though rate limiting and error handling are not mentioned.

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 consists of three concise sentences that front-load the purpose, followed by dependency and setup info. No wasted 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?

For a simple check tool with no output schema and no annotations, the description adequately covers purpose, external service, key parameter effect, and setup. It is complete given the tool's 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?

The input schema already has complete descriptions for all three parameters (100% coverage). The description adds value by noting that location affects AI Overview eligibility, which is not in 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 the verb 'check' and the resource 'AI Overview', and specifies the output 'which URLs it cites'. The purpose is distinct from sibling tools like 'am_i_cited' which check citations differently.

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 mentions the SerpAPI dependency and free tier limit, which informs usage constraints. However, it does not provide explicit guidance on when to use this tool versus siblings or when not to use it.

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