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

The description explicitly states that the body is discarded, which is a useful behavioral disclosure beyond the tool name. With no annotations available, it carries most of the behavioral burden, but it does not mention error behavior, redirect handling, timeouts, or rate limits.

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 clauses with no filler: it front-loads the main deliverable and adds one important behavioral caveat. 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?

For a tool with seven parameters, no annotations, and no output schema, this one-sentence description is too thin. It does not specify the output shape, how non-URL parameters are handled, or error semantics, so an agent may be left uncertain beyond the simplest URL-to-status case.

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?

All seven parameters already have descriptive schema entries, so schema description coverage is high. The tool description adds little parameter-level meaning beyond 'public URL,' and does not clarify how the unrelated parameters such as ref, city, or json relate to the actual HTTP fetch 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 precise deliverable — HTTP status and content type — for a public URL, and adds a non-obvious detail that the body is discarded. It is clear about the verb and resource, though it does not explicitly distinguish itself from similar 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?

The description implies when this should be used: when an agent needs HTTP status and content type for a public URL. However, it provides no when-not-to-use guidance and names no alternative tools, so it does not help an agent decide between web-fetch and a sibling like fetch-status.

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