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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose a meaningful behavior: the HTTP response body is discarded. However, it does not mention redirects, timeouts, error handling, or whether only 'public' URLs are accepted, leaving important behavioral gaps.

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 two short sentences, front-loads the core behavior, and contains no filler. It is appropriately concise for a simple intent, though the unusual schema may have warranted additional clarifying structure.

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 a complex seven-parameter schema and no output schema or annotations, the description is too sparse to be complete. It does not explain which parameter to pass, how the result is returned, or how this tool relates to its URL-focused siblings.

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 lists seven parameters, all with descriptions, but those descriptions are largely unrelated to the described tool (e.g., 'City name for a public weather hint', 'JSON text to validate') and the url description says 'normalize or cite' rather than fetch/status. The tool description does not clarify which parameters actually apply to web-fetch, so parameter selection is unreliable.

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 identifies the resource (a public URL) and the output (HTTP status and content type), and the 'Body discarded' qualifier adds specificity. It does not explicitly differentiate this from sibling tools like fetch-status, so it falls short of a 5.

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 use web-fetch instead of fetch-status, browser-url-ok, playwright-url-ok, or other URL-related siblings. The description gives no conditions or exclusions, so an agent has no help choosing between overlapping tools.

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