web_fetch

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

No annotations are provided, so the description carries the behavioral disclosure burden. It reveals an important environmental prerequisite (OLLAMA_API_KEY) and describes the return shape as a JSON-serializable dict with title, content, and links, which adds real context beyond the schema.

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 compact and organized with clear Args and Returns sections. Every sentence contributes necessary information, though the docstring-style formatting is slightly more verbose than a single crisp sentence.

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?

For a single-parameter tool with an output schema, the description provides the essential prerequisite, the URL requirement, and a summary of the return value. It does not discuss error behavior or when to prefer sibling tools, but the core details needed to invoke it correctly are present.

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?

Although the schema itself provides no description for url, the tool description explicitly explains that url is 'the absolute URL to fetch.' This adds meaningful format guidance beyond the bare string type and fully covers the only parameter.

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 a specific action and object: 'Fetch the content of a web page for the provided URL.' This distinguishes it from siblings like web_search, which finds pages rather than retrieving a specified page's content.

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 gives clear context for use: it fetches a provided URL and requires the OLLAMA_API_KEY environment variable. It does not explicitly contrast with alternatives like web_search, but the purpose and prerequisite are sufficiently clear.

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