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

The only behavioral disclosure is the negative statement 'No browser is launched.' It does not reveal side effects such as network requests, rate limits, or what happens with the input parameters. Most parameter descriptions mention 'discarded' or 'no access,' but these are not part of the main tool description, leaving significant behavioral ambiguity.

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 concise with only two sentences, but it omits essential information about the parameters and behavior. It is not overly verbose, but it is insufficiently structured given the large and confusing schema, so a middle score is appropriate.

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?

With 9 optional parameters and no output schema, the description does not provide enough context for an agent to understand how the tool works, what inputs are meaningful, or what result to expect. The mismatched parameter descriptions and lack of usage guidance make it incomplete for practical use.

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 contains 9 parameters, but their descriptions are inconsistent and often unrelated to URL checking (e.g., 'City name for a public weather hint,' 'JSON text to validate'). The descriptions do not clarify how these parameters affect the check, and they actively confuse the tool's purpose. The coverage is 100% but the meaning is poor.

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's purpose: 'Check whether a URL can be opened' and explicitly distinguishes from browser-based tools with 'No browser is launched.' However, it does not specify the method (e.g., HTTP request, DNS check) or how it relates to sibling tools like fetch-status or web-fetch, so it is slightly less than fully clear.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or scenarios where it is preferred over sibling tools such as normalize-url or playwright-url-ok.

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