Web Fetch

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

The description claims 'static HTTP' but the input schema includes a 'render' parameter with options 'browser', implying dynamic rendering is possible. This contradiction misleads the agent. No mention of authentication, rate limits, or what happens on failure.

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 sentence, which is concise but lacks structure. It is too brief to be self-sufficient and misses important details about parameters and behavior.

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 the tool has 7 parameters, 2 enums, and no output schema, the description is severely incomplete. It omits rendering behavior, output format, error handling, and performance considerations, leaving the agent with insufficient context.

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 only 14% (only 'url' has a description). The tool description adds no additional meaning to any parameter; it does not explain the crucial 'render' enum or other parameters. This fails to compensate for the sparse schema.

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 a URL and returns Markdown-style text, which is a specific verb-resource pair. However, it does not distinguish from sibling tools web_find and web_search, which likely search for content rather than fetch 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?

No explicit guidance on when to use this tool versus alternatives. There is no mention of when not to use it or any context hints about prerequisites or limitations relative to siblings.

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