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

The description does disclose 'No disk access,' which is a useful side-effect guarantee, but it says nothing about return values, errors, or whether anything else is mutated. Since no annotations are provided, this partial transparency leaves major behavioral questions unanswered.

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 and free of filler, but it omits necessary context and does not effectively front-load the important constraints. The mismatch between the description and the large parameter list makes the brevity a liability rather than a strength.

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 required parameters, no examples, and no explanation of how the unrelated fields are used. An agent cannot confidently predict what arguments to provide or what result to expect.

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?

Only the 'path' parameter aligns with the stated purpose; the other eight parameters have descriptions like 'discarded after the shape check' or 'discarded after the length check' without explaining why they exist or how they relate to path safety. The schema coverage is 100%, but the semantic coverage is very poor.

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 says only 'Check whether a path looks safe. No disk access.' but the input schema exposes nine unrelated optional parameters (ref, url, city, feed, host, json, zone, query), so it is not clear what the tool actually does with them or what 'safe' means. The tool name suggests path validation, but the schema undermines that purpose.

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 about when to use this tool instead of sibling tools such as browser-url-ok, normalize-url, or validate-json. The description gives no context for selecting it.

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