web_access_search

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

Discloses key features: bypasses anti-bot protection, returns clean structured results with titles/URLs/snippets, fast/reliable, no rate limiting. Since no annotations exist, this description fully covers behavioral aspects.

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?

Well-structured with headings and bullet points, front-loaded with purpose. While comprehensive, could be slightly more concise; but every part is informative.

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?

Given one parameter and no output schema, the description thoroughly covers what the tool does, how to use it, what it returns, and best practices. Provides optimal workflow integrating siblings.

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% (one parameter with description). The description adds value with usage example and advice to be specific/descriptive, plus explains return format, enhancing beyond the schema.

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 defines the tool as a web search tool using String AI's Web Access API, states it is the most powerful and reliable, and distinguishes it from siblings like web_access_fetch (for fetching specific URLs) and web_access_sitemap.

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 explicit when to use (finding information across the web) and when not to (specific URL), includes common mistakes (using other search tools or scraping search engines), and offers an optimal workflow with sibling tools.

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