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

No annotations provided, so description must disclose all behavior. It reveals pricing, result structure, and that it uses Serper for Google results. However, it lacks information on rate limits, error handling, or whether any side effects exist.

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?

Description is relatively short and front-loaded with key info: what it returns, cost comparison, query format. Every sentence adds value, though the query format hint could be more precise.

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 simple schema and no output schema, the description covers purpose, output structure, and pricing. However, it omits details about result limits, pagination, and the meaning of gl/hl parameters, leaving gaps.

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 coverage is 0% and the schema only includes parameter 'q'. The description mentions parameters 'gl' and 'hl' not present in the schema, causing confusion. It adds some meaning for 'q' as query but introduces inconsistency.

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 performs web search using Serper, returning top 10 organic results, answer box, and knowledge graph. It distinguishes from sibling tools like search_news by specifying it's a general web search.

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?

It indicates when to use (cheaper than Exa /search) and provides pricing details, but does not explicitly state when not to use or mention alternatives for specific search needs like news.

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