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. It mentions 'No browser is launched' but does not explain what the check actually does (e.g., network request, validation), what happens to the other parameters (they are described as discarded in the schema), or whether there are side effects. This is a significant omission for a tool with 9 optional parameters.

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 extremely concise (one sentence) and front-loaded with the core action, but it is under-specified for the tool's complexity. It omits necessary details about the URL input and the purpose of sibling parameters, so brevity comes at the cost of usefulness.

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 9 parameters, no annotations, no output schema, and a highly ambiguous purpose, this description is far from complete. It does not explain how the tool works, which parameters are required or relevant, what the return value indicates, or how it relates to siblings beyond the 'no browser' hint. An agent would have no confidence in calling 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 coverage is 100%, so the baseline is 3, but the description adds no clarity about which parameter is the URL to check and does not resolve contradictions: the 'url' parameter is described as 'HTTPS URL to normalize or cite' in the schema, not 'to check'. The description also fails to explain why many parameters are present if they are discarded, leaving the agent confused about parameter relevance.

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 ('Check') and resource ('whether a URL can be opened'), and the clause 'No browser is launched' distinguishes it from sibling tools like playwright-url-ok. However, it does not clarify which parameter is the URL or what 'can be opened' means (e.g., HTTP status, DNS, or format check), so it is not fully unambiguous.

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 compared to browser-based tools, but it does not explicitly name alternatives, state when to use this tool over them, or provide any exclusion conditions. The guidance is implied rather than explicit.

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