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

No annotations are provided, so the description must carry the transparency burden. It does disclose a key behavioral trait—body is discarded—and the public-URL scope. However, it doesn't mention behaviors like error handling, redirects, timeouts, or the fact that the schema includes many parameters that appear to be discarded. This is moderate useful but incomplete.

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 sentences, front-loaded with the main purpose ('HTTP status and content type') and the key caveat ('Body discarded'). Every word earns its place; it's appropriately concise for simple usage, though it omits necessary context about the schema.

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 a schema with eight parameters and no output schema, the description's single sentence is insufficient. It doesn't clarify the relationship between the URL-fetch behavior and the other parameters, nor what a successful call returns besides 'status and content type'. An agent lacks enough context to invoke the tool reliably.

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 input schema includes eight parameters, each with a description, but the tool description only talks about a public URL. It never explains whether the other parameters (ref, city, feed, host, json, path) are optional, mutually exclusive, or ignored by web-fetch. This leaves the agent unable to correctly construct a call and fails to add meaning beyond the schema.

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 function: fetch a public URL and return its HTTP status and content type, while discarding the body. This is a clear verb+resource pairing. It doesn't explicitly differentiate from sibling tools like fetch-status or browser-url-ok, but the core purpose is not vague or tautological.

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 contains no guidance on when to use this tool versus alternatives such as fetch-status or normalize-url. It neither states a preferred use case nor excludes siblings, so an agent can't make an informed choice from this definition alone.

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