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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It discloses only that no browser is launched; it does not say whether the tool makes a network request, performs a syntax/shape check, has side effects, or what it returns. This is insufficient for a check tool with no output schema.

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 padding, front-loading the core purpose and adding a useful constraint. It is appropriately terse, though the terseness contributes to the behavioral under-specification scored elsewhere.

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 9 parameters, no annotations, and no output schema, this one-line description is not complete. It fails to explain the return value, the nature of the check, how parameters beyond url relate to the tool, or when to use it. The only definite context is the no-browser guarantee.

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 schema already documents all 9 parameters and even notes that most are discarded. The prose description adds no parameter-level meaning, and the url parameter's schema wording ('normalize or cite') does not clearly connect to 'can be opened', but the high schema coverage earns the baseline 3.

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 clear action and target: checking whether a URL can be opened, and it adds a key qualifier ('No browser is launched') that separates it from playwright-url-ok. It does not specify what 'can be opened' means (HTTP reachability, URL syntax, or DNS resolution), so it is slightly ambiguous.

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 phrase 'No browser is launched' implies the tool is a lighter-weight alternative to browser-based checks like playwright-url-ok, but it never says when to choose this tool over fetch-status, normalize-url, or web-fetch. Usage guidance is only implicit, not explicit.

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