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

The only behavioral note is 'No browser is launched,' but it does not disclose whether a network request is made, what side effects occur, what success/failure looks like, or what the return value contains.

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 very short, but it is under-specified for a tool with nine parameters. The single sentence is not front-loaded with the most important usage information and leaves too much unsaid.

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?

There is no output schema, no return value description, no error explanation, and no mention of network usage or side effects. Given the tool's ambiguous name and many parameters, the description is not sufficient for an agent to use 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?

Each parameter has a short description, but most are unrelated to the stated purpose of checking a URL (e.g., city, feed, json, zone). Terms like 'discarded after the shape check' are unclear and do not explain how the parameters relate to the tool's main behavior.

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 general action ('Check whether a URL can be opened') but immediately undercuts it with 'No browser is launched,' leaving the actual mechanism unclear. It also does not distinguish this from sibling tools like browser-url-ok or fetch-status.

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 guidance on when to use this tool versus the many similar sibling tools. No conditions, prerequisites, or example use cases are provided.

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