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

The description does disclose one notable behavior: 'No browser is launched.' However, it does not clarify whether the tool performs a live network fetch, a syntactic shape check, or something else. The schema's repeated 'discarded after the shape check' phrasing suggests a non-executing validation, which partially contradicts the 'can be opened' wording. With no annotations, this ambiguity leaves important behavioral characteristics undisclosed.

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 sentences and gets to the point immediately: the primary verb, target resource, and a critical qualifier. It is economical and front-loaded. A slightly richer explanation of what 'opened' means would be helpful, but the structure itself is strong.

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 eight disparate parameters, no output schema, and no annotations, the description leaves too much unresolved. It does not explain which parameter to set for a given request, whether the parameters are mutually exclusive, or what result the agent should expect. Schema descriptions help per-parameter but do not compensate for the missing overall invocation context.

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 input schema provides descriptions for all parameters, so the baseline is 3. The tool description itself adds no parameter-specific meaning and, if anything, obscures the relationship between the URL-focused name and the wide variety of alternate inputs. Since schema coverage is high, the description's lack of param detail is acceptable, but the mismatch between description and param list prevents a higher score.

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 verb and resource: 'Check whether a URL can be opened.' This is clear and actionable. However, it does not distinguish itself from sibling tools like browser-url-ok or web-fetch, and the input schema includes many unrelated parameters (city, feed, json, path) that muddy the apparent URL-only purpose.

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 provided on when to use this tool versus alternatives. The only hint is 'No browser is launched,' which implicitly contrasts with browser-based checkers, but no sibling name or explicit condition is given. An agent must infer the applicable context.

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