web_search

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

With no annotations, the description must disclose behavior, but it only says 'Search the internet using Ollama's web search API.' It does not mention result truncation, character limits, maximum results, pagination, or API-specific constraints, leaving the agent without critical behavioral knowledge.

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 clear sentence that is front-loaded and free of extraneous text. However, it under-specifies the tool's behavior, balancing conciseness against completeness.

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 no output schema, no annotations, and four parameters, the description is critically incomplete. It fails to explain return values, parameter use, or tool-specific behaviors, leaving the agent to make unsupported assumptions.

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?

The input schema has four parameters with 0% description coverage. The description does not explain the meaning of query, truncate, max_chars, or max_results, relying on schema names alone, which forces the agent to guess semantics.

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 states 'Search the internet using Ollama's web search API,' which clearly identifies the action (search), resource (internet), and implementation (Ollama's API). This distinguishes it from sibling tools like web_fetch, though it doesn't explicitly compare against them.

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 is provided about when to use web_search versus web_fetch or cluesift_domain_fetch. The description lacks any contextual signals, alternatives, or exclusions, scoring a 2 for absent usage guidelines.

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