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

With no annotations provided, the description carries the full burden, and it uses the two sentences to disclose the key non-obvious behavior: the body is discarded and only status/content type are returned. It omits details like redirect handling and request method, but for a public read-only fetch these are minor.

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, front-loaded sentences with no filler. 'Body discarded' is a high-signal caveat that 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?

Despite the simple wording, the tool surface is not simple: nine optional parameters, no required fields, no output schema, and a crowded sibling set. The description does not tell an agent which parameter to supply or how web-fetch differs from fetch-status, browser-url-ok, or playwright-url-ok, making it materially incomplete.

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 baseline is 3. The description adds no parameter-level detail beyond saying the URL should be public, and it never explains how the other eight optional parameters relate to the declared HTTP-status behavior.

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 states a concrete outcome: HTTP status and content type for a public URL. The 'Body discarded' note distinguishes it from a body-returning fetch. It does not explicitly differentiate it from overlapping siblings like fetch-status or browser-url-ok, so it stops 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?

The description implies when to use the tool: when you need status and content type for a public URL. However, it provides no explicit when-to-use/when-not-to-use guidance and names no alternatives despite a sibling list that includes several fetch/check tools.

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