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

The description discloses one negative behavior: no browser is launched. It does not state whether the tool makes a network request, what side effects or errors may occur, or what 'can be opened' means operationally. With no annotations provided, this is insufficient behavioral transparency.

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 only two short sentences and places the main action first. It contains no redundant or filler content.

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?

Given the large optional parameter set and no output schema, the description does not explain the return value, how to interpret the result, or why most parameters are accepted and discarded. The tool is too underspecified for reliable invocation in complex contexts.

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 schema description, many are described as 'discarded' after unrelated checks, and the main 'url' parameter is described as 'HTTPS URL to normalize or cite' rather than a URL to open. This mismatches the stated purpose and leaves the agent unsure which of the nine optional parameters are actually relevant.

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 names a specific verb and resource: checking whether a URL can be opened, and the second sentence adds a distinguishing constraint: no browser is launched. It is not fully precise about what 'can be opened' means (HTTP response vs. page render), but the core purpose is 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?

No guidance is given about when to prefer this tool over siblings such as browser-url-ok, fetch-status, or normalize-url. The only usage hint is negative ('No browser is launched'), with no scenario or criteria stated.

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