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

With no annotations provided, the description carries the behavioral disclosure burden. 'Body discarded' is a useful disclosure that prevents the agent from expecting HTML, and it names the returned values. It does not cover errors, redirects, rate limits, or auth requirements, 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?

Two short sentences with no filler: the result, the URL scope, and the discarding behavior. The key constraint is front-loaded and every sentence earns its place.

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 schema contains eight parameters and there is no output schema or annotations. The description addresses only the url case and ignores ref, city, feed, host, json, and path; it also does not describe the response shape, so non-URL inputs remain confusing for an agent.

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 already describes every parameter, so schema coverage is effectively 100% and the baseline is 3. The description adds no parameter-level meaning and does not help an agent choose among the seven non-url parameters, but it does not misrepresent them.

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 purpose: return HTTP status and content type for a public URL, and it explicitly says the body is discarded. It avoids tautology, but it does not differentiate from close siblings 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?

The phrase 'for a public URL' and the stated output imply when to use it, but no alternative tools are named and no exclusions or prerequisites are given. Agents are left to infer the boundary with fetch-status and browser-url-ok.

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