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

With no annotations provided, the description must carry the behavioral burden. It states the HTTP method and result type but does not mention side effects, safety, error behavior, or response format details.

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 that immediately conveys the core action and output. No filler or redundant wording is present.

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?

While the tool is simple, the confusing parameter schema and lack of usage or output documentation leave an agent uncertain about which arguments are actually relevant and what a typical response looks like. The description does not compensate for the schema noise.

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 lists nine optional parameters with descriptions that appear irrelevant or copied from other contexts (e.g., 'Git ref name; discarded after the shape check', 'City name for a public weather hint', 'IANA timezone name'). Only 'url' aligns with the tool description, and even its description says 'normalize or cite' rather than 'check status'. This is misleading.

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') and resource ('a public URL'), and clearly indicates the output ('return status only'). This distinguishes it from content-fetching or URL-normalizing tools.

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 explicit guidance is given for when to use this tool versus alternatives such as browser-url-ok, web-fetch, or inspect-robots. The phrase 'status only' implies a narrow use case but does not clarify exclusion criteria.

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