Search The Web

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

Discloses key behaviors: headless execution, automatic search engine selection, and structured result page. With no annotations, this is adequate. Slightly less transparent on output specifics, but implicit in 'structure the result page'.

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, followed by critical usage guidance. No redundant words; every sentence serves a distinct role.

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?

Covers purpose, workflow, and key behavioral aspect. With output schema present, return values are handled. Could add brief note on error handling or timeout, but not essential for a search tool.

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%, so baseline 3. Description adds no extra parameter meaning beyond what the schema already provides. The mention of automatic engine selection is useful context but not parameter-specific.

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 verb 'Search', resource 'public docs/research web', and specifies headless execution with structured result for follow-up. Distinguishes from siblings like tb_search_open_top by explicitly mentioning it as a follow-up step.

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?

Provides clear context: search engine selection is automatic, and directs to use tb_search_open_top before read-view or extract. However, does not explicitly list alternatives or when not to use this tool, which would elevate to a 5.

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