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

With no annotations, the description carries the behavioral disclosure burden. It does usefully disclose that the response body is discarded, which is a meaningful non-obvious behavior. However, it does not mention error behavior, redirects, auth limits, return shape, or that most schema parameters are discarded, 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?

The description is a single tightly written sentence with no filler. The key output (status/content type) is front-loaded, and the body-discarded caveat is included efficiently. It earns its place without wasting tokens.

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 tool has 9 optional parameters, no output schema, no annotations, and many nearby sibling tools. The one-line description is insufficient to disambiguate which parameter matters and why the others exist, nor how this tool differs from fetch-status or browser-url-ok. The schema helps, but the description alone leaves important invocation context missing.

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 and the schema already explains each parameter individually. The description adds no parameter-level meaning and does not clarify why parameters like city, ref, json, and zone coexist with url, which leaves semantic ambiguity about how the tool should be invoked.

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 names a specific action and result: HTTP status and content type for a public URL, with the body discarded. This clearly distinguishes the tool from URL-normalization or browser-check siblings, though it does not explicitly name them. The large set of unrelated schema parameters slightly muddies the stated purpose.

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 about when to prefer this tool over siblings like fetch-status, browser-url-ok, or normalize-url. The phrase 'Body discarded' implies not to use it when body content is needed, but no explicit when-to-use/when-not-to-use direction or alternatives are provided.

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