research_all

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

No annotations provided, so description must carry behavioral disclosure. It mentions parallel fan-out and grouping by source, but lacks details on rate limits, authentication, error handling, or return format. For a read-only tool, more transparency is needed.

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, front-loaded with core purpose, no extraneous information. Every word adds 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?

Adequate for tool selection (distinguishes from siblings), but incomplete for invocation without output schema and missing parameter descriptions. Agent might guess defaults but lacks clarity on response format.

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 only 25% (just sources). The description adds default sources and brave condition, but does not explain the meaning of query, limit, or since_days parameters. This leaves significant ambiguity for an AI agent.

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?

Clearly states the tool fans out a query to multiple sources in parallel and returns aggregated results by source. The description distinguishes it from sibling tools (individual source researchers) by highlighting the parallel execution and aggregation.

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 lists default sources and conditionally includes brave based on API key. Implies when to use (multi-source search) versus single-source siblings, but does not explicitly state 'use this for cross-source queries; for single-source, use the specific tool.'

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