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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only discloses a negative trait (no browser launched) but omits what the tool actually does: whether it makes an HTTP request, what it returns, or if it has side effects. This is insufficient for a tool with no annotation safety profile.

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 a single terse sentence, which is concise in word count but fails to convey necessary information. It does not earn its place because it is under-specified—a vague statement that doesn't help an agent understand the tool's behavior or use case.

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 complexity of 9 parameters, zero annotations, and no output schema, the description is drastically incomplete. It doesn't explain what the tool returns, how parameters interact, or when to use it. An agent would be completely lost trying to call this tool correctly.

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 is 3. The tool description adds no parameter meaning—it doesn't clarify which parameter is the target URL or how the many seemingly unrelated parameters (city, zone, json, etc.) relate to the tool's purpose. However, since the schema already documents each parameter, the description doesn't degrade the semantics.

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 clear action (check whether a URL can be opened) and a constraint (no browser launched), but 'opened' is ambiguous—could mean HTTP reachability, DNS resolution, or something else. It does not distinguish this tool from siblings like browser-url-ok or fetch-status, so the purpose remains vague.

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 only usage hint is 'No browser is launched', which implies a lightweight check but does not explicitly state when to prefer this tool over alternatives. No conditions, exclusions, or alternative tool names are provided, leaving the agent to guess the appropriate context.

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