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

The only behavioral detail is 'Body discarded,' which is useful but minimal. With no annotations, the description does not disclose redirect handling, error behavior, rate limits, or whether content type includes charset, leaving significant behavioral ambiguity.

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 brief and front-loaded, and both sentences add information. However, it is too terse for a tool with nine unrelated optional parameters and no output schema, so the structure does not compensate for missing context.

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 no output schema, no annotations, and a large, incoherent parameter list, the description is far from complete. It does not explain return format, parameter selection, failure modes, or relationship to sibling tools.

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 the schema has per-parameter descriptions, they appear copy-pasted from unrelated tools (e.g., 'Git ref name', 'City name', 'JSON text to validate', 'IANA timezone name') and do not align with a web-fetch tool. The description does not clarify which of the nine optional parameters are relevant, so the input contract is effectively meaningless.

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 the tool returns HTTP status and content type for a public URL and discards the body, so the core purpose is inferable. However, it lacks an explicit action verb and does not distinguish this from related sibling tools such as 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?

There is no guidance on when to use web-fetch versus alternatives like browser-url-ok, playwright-url-ok, fetch-status, or inspect-robots. The description does not mention any conditions, preferences, or exclusions.

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