tavily_search

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

The description mentions a behavioral trait: 'rotates across multiple API keys', which is beyond the (missing) annotations. However, it omits other important details like rate limits, costs, or result format, which would be expected for a search tool.

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 succinct with two sentences. The first sentence clearly states the core purpose, and the second adds a key behavioral detail. No extraneous information is present.

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 5 parameters, no output schema, and no annotations, the description is too minimal. The agent lacks information about return values, pagination, or how to interpret results, making it insufficient for effective use.

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 schema coverage is low (20%), with only 'query' having a description. The description adds no information about parameters such as max_results, search_depth, include_answer, or include_raw_content, leaving the agent without guidance on their meaning or usage.

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 'Search' and the resource 'web using Tavily', which is a specific search engine. The purpose is unambiguous, and since there are no sibling tools, differentiation is not required.

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?

No guidance is provided on when to use this tool versus alternatives or when not to use it. The description only implies usage for web searches, but lacks exclusion criteria or context for decision-making.

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