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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state that the body is discarded, which is useful, and restricts to public URLs. However, it fails to mention any other behaviors: whether it follows redirects, rate limits, error handling, or what happens with non-public URLs. For a tool with no annotation coverage, this is a significant gap.

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 sentence with no wasted words, and the core purpose is front-loaded. It is appropriately sized for such a simple operation. However, it sacrifices necessary context for brevity, which prevents a 5.

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 and no output schema, yet the description only mentions URL and body. It does not describe the return format (beyond status and content type) or explain how the other eight parameters are used. For a tool with this parameter count, the description is severely incomplete; an agent cannot infer correct usage beyond the simplest case.

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 coverage is 100% and each parameter has a clear description, including which are discarded. The tool description adds no extra meaning beyond the schema; it does not clarify which parameter is primary (presumably url) or how multiple parameters interact. Since the schema does the heavy lifting, the baseline of 3 applies.

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 a specific verb and resource: retrieving HTTP status and content type for a public URL, with a note that the body is discarded. This is unambiguous about the core function. However, it does not explicitly distinguish itself from similar siblings like fetch-status or browser-url-ok, which could also fetch status, so it misses the differentiator requirement for a 5.

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 the many siblings (fetch-status, browser-url-ok, normalize-url, etc.). The description implies it is for quick status checks but does not state exclusions or alternatives. An agent is left to guess which of several similar tools fits, especially since the description does not mention edge cases like redirects, timeouts, or non-public URLs.

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