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

No annotations exist, so the description carries the disclosure burden. It usefully reveals that the body is discarded and that the URL must be public, but it omits redirect behavior, error handling, response format, and the fact that many schema parameters are discarded after shape checks.

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 two short sentences with no filler, and the core behavior is front-loaded. 'Body discarded' is a necessary clarification that 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?

For a tool with nine optional parameters and no output schema, this is too sparse. It does not state which argument(s) to use for the fetch, what the response structure looks like, or how to handle the many discarded parameters. An agent could easily call it with the wrong parameter or misinterpret the result.

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 adds minimal meaning beyond the schema: it clarifies that a public URL is the core input and that the body is discarded, but it does not explain how url relates to params like feed, host, json, path, city, query, ref, or zone.

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 communicates that the tool returns HTTP status and content type for a public URL, and explicitly states that the body is discarded. It does not, however, differentiate this from siblings like fetch-status, browser-url-ok, or normalize-url, and it lacks a strong verb like 'fetch' or 'check'.

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 this tool versus alternatives such as fetch-status, browser-url-ok, or normalize-url. The phrase 'public URL' hints at scope, but no conditions, exclusions, or alternative recommendations are provided.

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