tavily_search_context

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

No annotations exist. The description mentions automatic API key rotation, a behavioral trait, but fails to disclose whether the tool is read-only, destructive, or any other important behaviors. The return of 'context results' is vague.

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 concise with two sentences. The primary purpose is front-loaded. However, it lacks detail and could be more structured without becoming verbose.

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 11 parameters, no schema descriptions, and no annotations, the description is severely incomplete. It does not explain what makes this tool different from tavily_search, how parameters affect behavior, or what the output schema contains. The agent cannot fully understand how to use the tool effectively.

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?

With 0% schema coverage and 11 parameters, the description adds no meaning to any parameter. It does not explain key parameters like query, search_depth, topic, days, etc. The agent is left without guidance on how to fill these fields.

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 that the tool searches and returns contextual results with original content, and mentions automatic API key rotation. However, it does not distinguish itself from the sibling tool tavily_search, which likely offers a simpler search without content.

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 instead of alternatives like tavily_search or tavily_extract. The description implies it is for getting context with content but does not specify use cases or exclusions.

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