fetch_fetch

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

With no annotations provided, the description carries full burden. It discloses the key behavioral trait that HTML pages are automatically converted to plain text, which is useful. However, it does not mention other aspects like redirect handling, error behavior, or authentication needs. The conversion detail adds significant value.

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 concise with three short sentences, front-loading the purpose and key behavior. Every sentence earns its place with no extraneous text.

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 that an output schema exists, return format is covered. However, the description lacks parameter descriptions, which are essential for correct usage. It is adequate for a simple tool but incomplete in guiding parameter usage.

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 description coverage is 0% for 2 parameters, yet the description does not mention the 'url' or 'max_chars' parameters at all. It adds no meaning beyond the schema field names, leaving the agent without guidance on parameter format or constraints.

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 fetches text content from a URL and converts HTML to plain text, with a specific verb ('Fetch') and resource (URL). It distinguishes from sibling 'search' by stating 'Use search to find URLs; use fetch to read 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?

Explicitly tells when to use this tool ('to read a specific URL') and when to use the alternative 'search' for finding URLs. This provides clear usage guidance beyond implied context.

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