websearch

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It does not describe the return format, whether results include content or just URLs, rate limits, or how provider controls affect behavior. For a web search tool, this leaves important operational details undisclosed.

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 well-structured sentence that front-loads the core purpose, then lists required vs. optional parameters. No word is wasted, and it is easy to scan.

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 there is no output schema and no annotations, the description should explain what the tool returns and how the optional controls affect behavior. It only covers the basic invocation pattern, leaving significant gaps for an agent deciding whether and how to use the 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 60%, and the description only groups parameters as 'optional provider controls' without explaining their semantics. The enums for 'type' and 'livecrawl' are particularly ambiguous, and the description does not clarify what values like 'fast' or 'preferred' mean. It adds little beyond the schema's terse field descriptions.

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 purpose: 'Search the web through the configured Exa or Parallel provider.' This is a specific verb+resource pairing that distinguishes websearch from sibling tools like webfetch, which likely fetches a specific URL.

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 provides clear context for using the tool ('Search the web') and states that query is required while listing optional parameters. However, it does not explicitly mention when to use websearch over webfetch or other alternatives, so it lacks explicit exclusions.

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