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

The description discloses that no browser is launched, which is a useful behavioral note. However, with no annotations provided, it fails to mention other side effects such as whether a network request is made, whether external services are contacted, or whether any state changes occur.

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 front-loaded, stating the primary purpose in the first sentence and the key safety/behavioral constraint in the second. Every word adds value, and there is no unnecessary elaboration.

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?

The description lacks essential context: it does not specify the return value, how a successful or failed check is reported, whether network access is involved, or why many unrelated parameters exist in the schema. With no output schema and no annotations, this is insufficient for an agent to confidently use the tool.

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 description only concerns checking a URL, but the input schema includes eight additional loosely related parameters (e.g., city, feed, json, zone) that are not explained in the description. Even the 'url' parameter's schema description says 'normalize or cite' rather than 'check if open,' making the parameter semantics misleading and confusing.

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 checks whether a URL can be opened, and the phrase 'No browser is launched' helps distinguish it from browser-launching alternatives. It is concise and specific, though it does not detail what 'opened' means in terms of HTTP response or accessibility.

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 explicit usage guidance is given. The description does not say when to prefer this tool over similar siblings like browser-url-ok or fetch-status, nor does it mention any prerequisites or conditions for use. The only hint is that no browser is launched, but this is not framed as a usage recommendation.

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