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

The description discloses 'No disk access', which is a useful safety guarantee. However, it does not explain the tool's behavior for the other 8 parameters, nor its return value or side effects (e.g., whether it discards inputs, returns a boolean). Given no annotations are present, the description carries the full burden but fails to cover the tool's actual multi-parameter behavior.

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 a single efficient sentence, front-loading the core action and safety note. No unnecessary words. However, its brevity contributes to the incompleteness, but for what it does say, it is well structured.

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 required fields, no output schema, and no annotations, the description is severely insufficient. It does not explain what the tool returns, how to choose among parameters, or whether it validates only one field at a time. The tool's real behavior is largely unexplained, making it inadequate for correct invocation.

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%—every parameter has a meaningful description (e.g., 'Git ref name; discarded after the shape check'). The description adds nothing beyond the schema and does not clarify which parameter to use when. Since the schema already documents each parameter, a baseline of 3 is appropriate, but the description's path-only focus may mislead agents into ignoring the other fields.

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 clear verb and resource ('Check whether a path looks safe'), but the input schema contains 9 unrelated parameters (url, city, json, zone, query, etc.) that the description does not mention. This creates ambiguity about the tool's actual scope—it appears to be a generic shape-checker but is described and named as a path-specific validator. The mismatch between description and schema undermines clarity.

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 provides no guidance on when to use this tool versus its many siblings (browser-url-ok, validate-json, wiki-title-ok, etc.). It does not specify which parameter to pass for different input types or exclude alternatives. An agent has no basis to decide whether to invoke this tool instead of a more specific one.

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