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

With no annotations, the description carries the full behavioral burden. It does disclose that the body is discarded, which is useful, but it omits other important traits: whether a real network request is made, how redirects or errors are surfaced, and that most schema parameters are ignored after shape checks. The output is only described as 'HTTP status' without clarifying format.

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 only two short sentences with no filler, and the key idea 'HTTP status' is front-loaded. 'Body discarded' is a useful secondary fact. It is concise as prose, even though it is under-specified relative to the complex 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?

For a tool with nine optional parameters, no output schema, no annotations, and many overlapping siblings, this description is far from complete. It does not specify the return shape, the meaningful argument, or how this tool relates to fetch-status, web-fetch, or browser-url-ok.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds no parameter-level meaning and actually conflicts with the schema. It refers to a 'public library docs URL' while the `url` parameter is described as an 'HTTPS URL to normalize or cite', and every other parameter is marked discarded. An agent cannot reliably determine which parameter is the intended input.

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 conveys that the tool returns an HTTP status and discards the body, but it is a noun phrase rather than a clear verb+resource statement. 'Public library docs URL' is ambiguous and does not map cleanly to the schema's generic `url` parameter, nor does it distinguish this tool from siblings like fetch-status or web-fetch.

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 this tool versus alternatives. There are no sibling mentions, no exclusions, and no indication which of the nine optional parameters should be supplied. 'Body discarded' hints that it is for status-only checks, but the selection criteria are never explicit.

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