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

With no annotations, the description carries the full burden of behavioral disclosure, but it only reveals that no browser is launched. It does not state whether a network request is made, what the result looks like, whether redirects are followed, or how failures are reported. The schema hints that unrelated parameters are discarded, but the description itself is silent.

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 two short sentences with no fluff, front-loading the core operation and then the key no-browser qualifier. It is efficient, though it is arguably too terse for a tool with nine optional parameters.

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 agent still does not know what return value to expect, which of the nine optional parameters should be populated, or how this tool relates to sibling checking tools. Given the absence of an output schema and annotations, the description leaves too much to inference for reliable invocation.

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 the baseline applies: every parameter is already documented, including explicit 'discarded' notes for decoy fields. The description itself adds no parameter guidance, and the 'url' parameter description mentioning 'normalize or cite' is somewhat inconsistent with the tool's stated purpose, which slightly weakens clarity.

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 operation: 'Check whether a URL can be opened.' It adds a useful qualifier, 'No browser is launched,' which helps separate it from a browser-driven check like playwright-url-ok. It stops short of a 5 because it never names the alternative or defines what 'can be opened' means in practical terms.

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?

There is no guidance about when to use this tool versus siblings such as playwright-url-ok, web-fetch, or fetch-status. No prerequisites, exclusions, or alternative selection conditions are provided, so an agent must infer the intended usage.

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