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

With no annotations, the description carries the full burden and does disclose an important behavior: the HTTP body is discarded. It also limits scope to public URLs. However, it does not mention redirect handling, error behavior, response format, or whether any headers/auth are needed, so transparency 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?

A single sentence, front-loaded with the core value and ending with the important body-discarded caveat. It has no filler and is easy to scan, though it sacrifices some necessary detail for brevity.

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?

There are no annotations, no output schema, nine optional parameters, and several closely related sibling tools, yet the description is only one line. It does not specify the return structure, which parameters to populate, or when not to use this tool, leaving significant ambiguity for reliable invocation.

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; the description correctly emphasizes URL as the core concept. However, it does not clarify how the other eight optional parameters relate to a URL fetch, and the schema's `url` description ('normalize or cite') conflicts with the fetch behavior, leaving the description unable to resolve that confusion.

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 identifies the tool's core output: HTTP status and content type for a public URL, with the body discarded. It conveys a fetch/check operation even without an explicit verb, and the 'Body discarded' clause distinguishes it from full-content retrieval tools. However, it does not explicitly mention which parameter to use or differentiate from the sibling `fetch-status` tool.

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 phrase 'public URL' and 'Body discarded' imply this is for lightweight status/content-type checks rather than full page fetching. But the description does not name alternatives or provide explicit exclusions, so an agent must infer when to use this instead of `fetch-status`, `browser-url-ok`, or `playwright-url-ok`.

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