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

With no annotations, the description carries the full behavioral burden. It discloses the HTTP method (HEAD), the public scope, and the minimal output. It does not mention redirects, timeout behavior, or error handling, but the core behavior is transparent enough for a simple status check.

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, compact sentence with no filler or redundant wording. It is highly scannable and directly conveys the tool's action and output.

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 appears simple, but the input schema is complex with many unrelated optional parameters and no output schema. The description does not explain how the parameters relate to the HEAD request, what status format is returned, or how to pick the correct input. This leaves important context missing 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 schema has 9 optional parameters, all with descriptions that seem copied from unrelated tools. The description does not clarify which parameter is the target URL, and the 'url' parameter is described as 'HTTPS URL to normalize or cite' rather than a URL to head. This ambiguity makes it unclear how to correctly invoke the tool.

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 verb (HEAD), the target (a public URL), and the result (status only). It is easy to distinguish from sibling tools like web-fetch, which returns page content, and status-catalog, which lists status codes.

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 'return status only' implies this is for when only an HTTP status is needed, but it does not explicitly explain when to use this tool over alternatives or call out exclusions. The guidance is adequate but not detailed.

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