search_google

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

Discloses return format (JSON with title, URL, snippet), additional result types depending on search type, and credit cost (light vs full). No annotations provided, but description covers key behavioral aspects without contradictions.

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?

Three concise sentences, front-loaded with purpose, then output details, then usage guidance. Every sentence adds value, 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?

Complete for a search tool: covers what it does, output structure, parameter semantics (via schema), usage context, and cost. No output schema, but description adequately describes returned data.

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 has 100% coverage, but description adds context on credit cost for light_request and explains result types (top stories, knowledge graph) that depend on search_type, adding value beyond schema descriptions.

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 explicitly states 'Search Google' and mentions returning structured results as JSON, clearly distinguishing it from sibling tools that search specific platforms like Amazon or Reddit.

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 clear guidance: 'Use when the user asks to search the web, find current information, or look something up online.' Does not explicitly list exclusions, but the sibling context implies when not to use.

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