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

With no annotations provided, the description carries the transparency burden, and it does disclose that the tool operates only on public URLs and returns status only. However, it omits important behaviors like redirect handling, timeout behavior, or error conditions, leaving significant gaps.

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 concise sentence that gets straight to the point. It is well-structured and front-loaded with the essential action.

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 description is far from complete given the complex and confusing schema. It does not explain why the schema contains nine unrelated optional parameters, nor does it clarify which parameters the tool actually uses. The lack of an output schema also leaves the return format unspecified.

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?

Despite high schema coverage, the parameter descriptions are inconsistent with the tool's stated purpose. The schema includes unrelated fields (Git ref, city, timezone, search text) with descriptions like 'discarded after the shape check' that are confusing and misleading for a URL status 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 tool performs a HEAD request on a public URL and returns only the status. This is a specific, unambiguous statement of the tool's core function.

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 description gives no guidance on when to use this tool versus the many sibling tools such as browser-url-ok, playwright-url-ok, or web-fetch. There is no mention of alternatives, use cases, or exclusions.

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