web_search

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

No annotations provided, so description bears full burden. It discloses no fallback behavior and required environment variable. Also describes return structure. Does not mention rate limits or pagination, but search tools typically have these; still, adds value beyond an empty description.

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?

Two sentences, no filler. All information is directly relevant and front-loaded.

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?

With 5 parameters and no description for them, the tool is incomplete. However, the output schema exists (not shown), so return value explanation is less needed. The description covers purpose and a key constraint but lacks parameter guidance.

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 0% description coverage and 5 parameters. Description does not explain any parameter (e.g., search_depth, topic, include_answer). It only mentions the optional synthesized answer. This leaves the agent guessing about parameter effects.

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 it searches the web using Tavily and returns titles, URLs, snippets, plus an optional answer. Distinguishes from sibling 'web_fetch' which fetches a specific page, not 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?

Mentions the API key requirement and no fallback, implying use when Tavily is accessible. Does not explicitly exclude scenarios or compare with alternatives, but the context is clear enough.

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