web_search

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

The description mentions the tool uses a 'local SearxNG instance', which hints at infrastructure but does not disclose rate limits, authentication, error handling, or other behavioral traits. There are no annotations to supplement, so the description carries the burden but only partially meets it.

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 concise sentences that front-load the core purpose and output. No unnecessary words. Efficient communication.

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?

With 8 parameters and no output schema, the description provides basic purpose but lacks context on parameter interactions, result structure (beyond mentioned fields), or differentiation from sibling. Adequate but not thorough.

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 coverage is 100% with clear parameter descriptions. The description adds no new parameter details beyond summarizing the return format. Baseline 3 applies given full schema coverage.

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 action ('Search the web'), specifies the resource ('local SearxNG instance'), and describes the output ('titles, URLs, and snippets'). It effectively distinguishes from the sibling tool 'web_fetch' (page fetching vs. search).

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 implies general web searching but does not provide explicit guidance on when to use this tool over siblings (e.g., for multi-result search vs. single-page fetch). No when-not-to-use or alternatives mentioned.

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