search_all

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose that results are deduped, which is useful, but it does not mention any other behavioral traits such as whether the operation is read-only, whether it requires authentication, how errors are handled, or what 'every source' concretely means. This is a minimal level of transparency.

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 a single, clear, and front-loaded sentence with no wasted words. It conveys the core action and result type efficiently. While it is short, conciseness is about structure and economy, which this achieves perfectly.

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?

Although the tool has an output schema to describe return values, the description is incomplete for a tool with 3 parameters and no annotations. It lacks usage guidance, parameter semantics, and a clear definition of 'every source'. It does not explain the max_results parameter or how sources can be restricted, making it inadequate for an agent to select and invoke this tool confidently.

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 schema has 0% description coverage, and the description does not compensate by explaining any of the three parameters (query, sources, max_results). It does not even implicitly clarify the meaning of 'sources' beyond the phrase 'every source' or mention the max_results limit. The agent must rely solely on parameter names and defaults, which is insufficient for correct invocation.

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 indicates the tool fans out a query to every source and returns deduped SearchResult dicts, which distinguishes it from the sibling tools (research, scrape_url, rerank_docs, summarize_docs). The verb 'fan out' is specific, and the resource ('every source') is named. However, it does not explicitly say 'search', relying on the word 'query' and the return type to convey the core purpose.

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 given about when to use this tool vs. alternatives. It does not mention any sibling tools, nor does it state explicit conditions such as 'use when you need results from all sources'. The phrase 'every source' implies comprehensive search, but there is no clear 'when' or 'when not' guidance.

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