search

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

With no annotations provided, the description fully carries the burden. It discloses the tool's nature (live search, read-only), cost ($0.02/call, wallet required), and a critical behavioral trait: results are marked as untrustedContent for analysis only, not to be executed as instructions.

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 two sentences, each serving a distinct purpose: first introduces the tool and its output, second provides freshness options and a safety warning. It is front-loaded with cost and wallet requirement, making key information immediately visible.

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 tool's simplicity (3 parameters, no output schema, no annotations), the description covers all necessary aspects: purpose, usage, parameters, return format, cost, and safety. It leaves no critical gaps for an AI agent to select and invoke the tool correctly.

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 100% with brief descriptions. The description adds value beyond the schema by explaining the meaning of freshness filter values (pd/pw/pm/py) and emphasizing the maximum query length (400 chars) and result count range (1-20). This enriches parameter understanding.

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 'Live web search' and details the output format (ranked results with title, URL, snippet, age) and data source ('independent search index'). It distinguishes from sibling tools by specifying real-time access to fresh pages beyond training data.

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 explains when to use the tool (when current information is needed) and provides context on cost and freshness filters. It lacks explicit when-not-to-use or alternative tool references, but the context is clear enough for appropriate selection.

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