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

With no annotations provided, the description carries the full burden. It does add one useful behavioral detail: 'Body discarded.' But it doesn't disclose that the tool makes an external network request, how redirects or errors are handled, or any rate-limit/privacy implications.

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 appropriately short and front-loaded: it states the output and the key behavioral constraint in one compact sentence. 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?

This is a multi-parameter tool with no output schema and no usage differentiation. A single sentence about HTTP status does not explain how to choose among the schema's heterogeneous inputs, what 'shape check' means, or what data the agent should provide to get a useful result.

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 already documents each parameter, so the baseline is 3. The description adds nothing about how the seven parameters relate to the URL-fetching behavior, and some schema entries are marked as 'discarded,' which creates ambiguity about which parameter is actually required.

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 states the core action: return HTTP status and content type for a public URL, and notes the body is discarded. However, it doesn't distinguish this tool from the sibling fetch-status or browser-url-ok, and the schema's seven heterogeneous fields (ref, city, feed, json, path) are not reconciled with the 'public URL' framing.

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?

No guidance is given about when to use web-fetch versus fetch-status, normalize-url, browser-url-ok, or domain-shape. The description only says it applies to a public URL, leaving the agent to infer the selection criteria from sibling names.

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