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

With no annotations present, the description carries the full burden and does disclose one meaningful behavior ('Body discarded', implying a lightweight check that does not return page content). However, it omits other traits like redirect handling, TLS behavior, timeouts, error cases, or whether the fetch is a plain GET, so disclosure is only 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 a single tight 10-word sentence with the key information front-loaded. It is not bloated, though the extreme brevity leaves gaps that a slightly longer description could have closed.

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 9 parameters and no output schema, the description fails to clarify why parameters like city, zone, ref, or query exist for a web-fetch tool, and it does not describe the response format beyond a bare mention of status and content type. Error behavior, redirects, and parameter relevance are entirely absent, leaving the tool under-specified for an agent.

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?

Although schema description coverage is 100%, the parameter descriptions are actively misleading and appear copy-pasted from unrelated sibling tools: ref (Git ref), city (weather hint), feed (RSS/Atom), zone (IANA timezone), json (validation), path (file check), and query (search length) have no plausible relation to fetching a URL's HTTP status. Even 'url' is described as 'normalize or cite' rather than fetch, so an agent cannot reliably map parameters to this tool's actual purpose.

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 specific action and resource ('HTTP status and content type for a public URL') and adds a distinguishing constraint ('Body discarded'). However, it does not differentiate from siblings like fetch-status or browser-url-ok, which likely perform similar URL-fetching checks.

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 provided on when to use this tool versus alternatives such as fetch-status, normalize-url, or inspect-robots. There is no 'use this when' context, leaving the agent to guess which sibling covers which scenario.

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