tavily-mcp-python

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

With no annotations provided, the description carries full burden of behavioral disclosure. While it mentions 'real-time results' and 'customizable parameters,' it doesn't address important behavioral aspects like rate limits, authentication requirements, error conditions, or what format the results come in. For a complex 14-parameter search tool, this is insufficient behavioral context.

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 efficiently structured in two sentences that convey core functionality and ideal use cases. It's appropriately sized and front-loaded with the main purpose, though could be slightly more concise by combining related concepts.

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 complex search tool with 14 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the output looks like, doesn't mention rate limits or authentication, and provides minimal behavioral context. The description should do more to compensate for the lack of structured metadata.

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 100%, so the schema already documents all 14 parameters thoroughly. The description mentions 'customizable parameters for result count, content type, and domain filtering' which aligns with some parameters but doesn't add significant meaning beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose as 'web search' with specific details: it uses Tavily's AI search engine, provides real-time results, and returns relevant web content. It distinguishes from siblings by focusing on search rather than crawling, extraction, or mapping.

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 provides clear context for when to use this tool ('gathering current information, news, and detailed web content analysis'), but doesn't explicitly mention when NOT to use it or directly compare to sibling tools like tavily-crawl or tavily-extract. The guidance is helpful but lacks explicit alternatives.

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