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

With no annotations, the description carries the full behavioral disclosure burden. It discloses a 20-request-per-minute rate limit and notes that output is a detailed research response, but it doesn't mention potential latency, authentication, side effects, or output structure, leaving gaps.

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?

Three focused sentences that front-load the purpose, then usage trigger, output type, and rate limit. There is no filler; every sentence provides operational value.

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 2-parameter tool with a rich schema and no output schema, the description gives core context—when to use, what it returns, and rate limiting. However, it doesn't specify the form or structure of the 'detailed response' or contrast with the sibling search tool, leaving some ambiguity for agent invocation.

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 input schema covers both parameters with descriptions (100% coverage), including enum semantics for 'model'. The description adds no additional parameter-level meaning, so the baseline score of 3 applies.

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 opens with a specific action ('Perform comprehensive research...') and scope ('topic or question'), clearly distinguishing it from simpler search tools by emphasizing multiple sources and a detailed response. However, it doesn't explicitly name or contrast with sibling tools like tavily_search, so sibling differentiation is only implicit.

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?

Explicitly states 'Use this tool when you need to gather information from multiple sources...', giving a clear trigger condition. It lacks when-not-to-use guidance or alternative tool names, so it falls short of a full 5.

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