Tavily Search

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds valuable context about the credit cost structure and the disabling of automatic parameter selection, which goes beyond annotation data and clarifies a potential gotcha.

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: the first states the purpose cleanly, the second covers cost and selection behavior. No redundant phrases, and the most important caveat is 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?

For a 10-parameter tool with an output schema and annotations, the description effectively communicates the key non-obvious aspect (credit cost and advanced selection). Other details like date constraints are left to the schema, which already provides them. The description is sufficient for an agent to understand and safely invoke the tool.

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 description coverage is 70%, so most parameters are already documented. The description adds nuance to the search_depth parameter by stating that Advanced costs 2 credits and must be explicitly selected, and that automatic upgrades are disabled. This is more contextual than the schema alone provides.

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 'Search the public web with Tavily' with a specific verb (search) and resource (public web). It also distinguishes between Basic and Advanced search modes, providing scope. Since there are no sibling tools, no differentiation is needed.

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 gives explicit guidance on the default search mode (Basic), the cost difference, and that Advanced must be manually selected. It also warns that automatic parameter selection is disabled, which helps the agent avoid unexpected credit usage. No alternative tools are listed, so 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.