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

There are no annotations to lean on, and the description discloses only that it uses HEAD and returns status; it does not mention redirects, timeouts, error behavior, or that the many other schema parameters appear to be ignored.

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 very concise and front-loaded, but it is almost too terse; the large, irrelevant parameter list in the schema undermines the structural clarity.

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 nine optional parameters and no output schema, but the description does not specify the output format (e.g., numeric status code), which parameter is actually used, or why the other parameters exist; this leaves critical 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?

Although every parameter has a description, those descriptions are largely unrelated to the tool's stated purpose—e.g., 'url' is described as 'HTTPS URL to normalize or cite', and params like 'ref', 'city', 'feed', 'json', 'zone', and 'query' are described as discarded or tied to other tools, actively misleading an agent about their role.

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 states a specific verb (HEAD), a specific resource (a public URL), and a precise output (status only), which clearly distinguishes it from sibling tools like normalize-url or web-fetch.

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?

No guidance is given about when to choose this tool over alternatives, nor any conditions or caveats for use; the description simply states what it does without usage context.

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