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

The description discloses one behavioral aspect (no browser is launched), but it does not mention whether the tool makes network requests, whether it is read-only, or what side effects might occur. With no annotations to fill the gap, the agent is left guessing about the operational implications.

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 and well-structured: a clear subject-verb-object statement followed by a short negative qualifier. There is no fluff or redundant wording.

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 9-parameter schema with no required fields and no output schema, the description is too incomplete. It does not say what the tool returns, how to pass the URL, or how this tool differs from siblings like playwright-url-ok and web-fetch. This leaves substantial ambiguity for an agent attempting to invoke it 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?

Although the schema has descriptions for all 9 parameters, those descriptions are generic and often inconsistent with the tool's stated purpose. For example, the 'url' parameter is described as 'HTTPS URL to normalize or cite', which conflicts with 'check whether a URL can be opened'. The tool description itself does not clarify which parameter actually matters.

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 the tool's core purpose: checking whether a URL can be opened, and explicitly notes that no browser is launched. This makes the primary function easy to understand, though it does not specify the return value or which parameter to use.

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 description gives no direct guidance about when to use this tool versus closely related siblings like playwright-url-ok, normalize-url, or fetch-status. The statement 'No browser is launched' only weakly implies a distinction from browser-launching tools, but no explicit alternatives or selection criteria are provided.

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