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

The only behavioral disclosure is 'No browser is launched,' which clarifies a non-action but is minimal. No annotations are provided, so the description carries the full burden. It does not explain what 'can be opened' means (syntactic validity vs. reachability), what happens when multiple parameters are supplied, or what the return value looks like. This is insufficient for a tool with 9 diverse inputs.

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 short (one sentence), which is concise in length but under-specified in content. It front-loads the URL check but omits essential details about the tool's broad parameter handling. Conciseness is not valuable when it sacrifices necessary information—this is under-specification rather than efficient brevity.

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?

With 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It only addresses URL checking while ignoring the other 8 parameter types. There is no explanation of how the tool processes these varied inputs, whether they are mutually exclusive, or what the expected output is. An agent cannot confidently call this tool for anything beyond a basic URL check.

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 schema already documents each parameter (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no parameter-specific meaning beyond what the schema provides. Baseline is 3 because the schema does the heavy lifting; the description contributes nothing extra.

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 'Check whether a URL can be opened,' which is a specific verb and resource. However, the input schema accepts 9 diverse parameters (url, json, path, zone, etc.) that go well beyond a URL check. The description is misleading about the tool's actual scope, as many parameters are unrelated to URL validation. This is a clear mismatch between the described purpose and the actual capability.

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 vs. siblings like domain-shape, file-path-ok, validate-json, or normalize-url. The description does not mention any conditions, exclusions, or alternatives. An agent would have no idea whether to pick this tool over the specialized siblings for a given input type.

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