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

With no annotations to rely on, the description correctly takes on the safety/behavior burden by stating the operation is limited to HTTP status and content type and that the body is discarded. It does not mention redirects, timeouts, or method semantics, but the core non-destructive behavior is clear.

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?

Two short sentences with no filler; the result ('HTTP status and content type') is front-loaded and the key limitation ('Body discarded') is stated immediately after. Every word earns its place.

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?

A 9-parameter, 0-required, no-output-schema tool with no annotations needs more context than this. The description does not explain the relationship between the URL fetch and the unrelated optional params, what happens with no arguments, or the expected return shape.

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 100%, so the schema already explains every parameter, including which values are discarded. The tool description adds no parameter-level meaning and does not clarify why url, feed, host, json, path, zone, query, etc. all belong to one HTTP-status tool.

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 names a concrete resource (public URL) and the two outputs (HTTP status, content type), and explicitly says the body is discarded. It is specific enough to show what the tool does, though it does not distinguish web-fetch from siblings like fetch-status or normalize-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?

There is no guidance about when to choose web-fetch over fetch-status, browser-url-ok, normalize-url, or the other shape-check siblings. The only implicit cue is the qualifier 'public URL', which weakly suggests it is for unauthenticated fetches.

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