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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose one behavioral trait ('No browser is launched'), but it omits side effects, network behavior, result format, and the fact that most parameters are discarded after the check. The schema says values are discarded, but that context is not in the tool description itself.

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 extremely short and front-loaded: the primary action appears first and the key qualifier 'No browser is launched' appears second with no filler. It loses a point only because the brevity leaves out important contextual information.

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?

For a tool with nine heterogeneous optional parameters, no annotations, and no output schema, a one-line description is not enough. The agent is left without guidance on which parameter to supply, what the return value looks like, or why non-URL parameters exist. Some useful context does exist, so this is not a 1.

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?

Schema description coverage is 100%, so every parameter already has an explanatory description. The tool description adds no parameter-level meaning, but the baseline of 3 applies because the schema is doing the heavy lifting.

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 concrete action and object ('Check whether a URL can be opened') and adds a useful qualifier ('No browser is launched'). However, it does not match the tool's actual input surface: the schema lists nine unrelated optional parameters such as city, feed, json, zone, and query, so an agent cannot tell whether this is a URL reachability check, a multi-purpose validator, or a shape-checking utility.

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 browser is launched' provides an implicit usage signal, especially alongside siblings like browser-url-ok, suggesting this is a lighter-weight check. But the description never names alternatives, gives explicit when-to-use/when-not-to-use conditions, or explains how it differs from normalize-url, fetch-status, or web-fetch.

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