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

With no annotations provided, the description carries the disclosure burden. It does reveal an important behavioral trait—'Body discarded'—which prevents agents from expecting page content, and it restricts the target to public URLs. However, it does not mention redirect handling, timeouts, user-agent behavior, or error/status semantics, so disclosure is partial.

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 exactly two short sentences with no filler; the primary function is front-loaded and the behavioral caveat earns a second sentence.

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?

For a network tool with no annotations and no output schema, this is incomplete. It states the two output values but not their format, error behavior, or which schema parameter to supply, and the schema's seven loosely-related optional fields create confusion that the description does not resolve.

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 provides descriptions for all seven parameters, so the baseline is 3. The tool description adds little parameter-specific meaning beyond implying the 'url' field, and it does not resolve which of the multiple URL-ish fields such as url, host, or feed is appropriate for web-fetch.

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 that the tool returns HTTP status and content type for a public URL and explicitly notes the body is discarded, making the core purpose clear and distinguishing it from a status-only sibling like fetch-status. It lacks an explicit action verb such as 'fetches' or 'returns', so it stops short of a fully specified 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 on when to choose web-fetch over comparable siblings such as fetch-status, browser-url-ok, playwright-url-ok, or normalize-url. The only usage hint is 'public URL,' which excludes private/internal resources but gives no explicit alternatives or when-not-to-use conditions.

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