info_search

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

No annotations, so the description must cover behavioral traits. It discloses the return format and parameter behaviors but does not mention rate limits, permissions, or potential result variability.

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 cover purpose and all parameters efficiently. No extraneous words, and the structure is front-loaded with the primary action.

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 an output schema exists (signal), the description adequately covers input parameters and return summary. Lacks comparison to siblings, but for a simple search tool it is nearly complete.

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 0%, but the description explains each parameter: query, count (with range 1-50), and recency (with valid values). This adds significant value beyond the schema's type/default.

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 'Search the web' and specifies the return type (titles, links, snippets), which distinguishes it from sibling tools like info_news (news search) and info_scrape (scrape specific pages).

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 on when to use this tool vs alternatives. No mention of when not to use or which sibling to use for different contexts (e.g., news vs. general search).

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