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

The description discloses that the body is discarded and that the URL should be public, which gives some behavioral transparency. However, with no annotations and no mention of network behavior, redirects, timeouts, or error handling, the full burden is not fully met.

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 extremely concise and free of fluff, capturing the essential behavior in a single 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?

The description is too sparse given the confusing multi-parameter schema. It does not explain which parameter is the URL, how the response is structured, or what edge cases might occur, leaving the agent without enough context to reliably invoke the tool.

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 lists nine optional parameters, most of which are irrelevant or contradictory to the web-fetch purpose (e.g., ref, city, feed, zone). The descriptions do not clarify which parameter should be used for the URL, and the tool description adds no guidance, making parameter selection highly ambiguous.

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 tool's core function: retrieving HTTP status and content type for a public URL while discarding the body. It is specific about the resource and output, though it does not explicitly distinguish itself from sibling tools 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?

No guidance is provided about when to use this tool versus alternatives. The description implies use for status/content-type checks, but does not mention exclusions, such as when body content is needed or when another sibling tool would be more appropriate.

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