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

With no annotations at all, the description carries the full burden of disclosing behavior. It does usefully state 'No browser is launched,' but it omits whether a network request is made, what happens on inaccessible URLs, whether any data is returned, and whether there are side effects or rate limits. For a tool that checks URL openability, these are material gaps.

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 short, front-loaded, and contains no fluff. Both sentences earn their place, though the extreme brevity leaves important context unaddressed, preventing a perfect score.

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 a 9-parameter schema, zero required parameters, no output schema, and no annotations, a two-sentence description is far from complete. It does not explain which parameters to provide, what the result looks like, or how the check is performed, leaving an agent without enough context to invoke it reliably.

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 even though the description adds no parameter-specific insight. However, the description focuses only on 'URL' while the schema exposes 9 optional parameters including city, json, query, and path, which could confuse selection. The schema itself carries the parameter meaning, so no additional credit or penalty beyond the baseline is warranted.

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 clearly states a specific action ('Check') and resource ('a URL'), and the qualifier 'No browser is launched' helps position it against sibling tools like playwright-url-ok. However, 'can be opened' is somewhat ambiguous—it doesn't specify whether this means HTTP reachability, DNS resolution, or browser rendering—so it doesn't fully earn a 5.

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 explicit guidance on when to use this tool versus alternatives such as playwright-url-ok, fetch-status, normalize-url, or web-fetch. The only implicit hint is 'No browser is launched,' which suggests it is not for browser-dependent checks, but no sibling is named and no selection criteria are given.

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