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

The description discloses a meaningful behavioral trait: 'Body discarded.' This goes beyond what the schema states and is useful safety-relevant context. However, with no annotations and no output schema, it does not mention redirects, failure behavior, network side effects, or how non-URL parameters are handled.

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 exceptionally concise and front-loaded, with every word contributing. It earns high marks for efficiency, though the brevity omits enough context to be considered a model structural example.

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 eight heterogeneous parameters, no annotations, no output schema, and several close sibling tools, a single sentence about HTTP status and content type is insufficient. Missing guidance about input selection, return shape, and tool differentiation makes misuse likely.

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 schema already describes each parameter individually, so the coverage is high and the description need not restate them. But the description does not clarify the relationship between the 'public URL' operation and the many alternative parameters such as ref, city, json, and path, leaving the agent uncertain about which parameter is the intended primary input.

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 operation: retrieving HTTP status and content type for a public URL, and it adds that the body is discarded. It does not, however, differentiate itself from sibling tools such as fetch-status or normalize-url, and the schema's many non-URL parameters make the exact scope slightly fuzzy.

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?

There is no guidance on when to use web-fetch versus alternatives like fetch-status, browser-url-ok, or normalize-url. The only implicit cue is 'public URL,' which is not sufficient for an agent to decide among the closely related sibling tools.

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