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

There are no annotations, so the description bears the burden of explaining side effects, return values, and error behavior. It only discloses 'No disk access' and never states what the tool returns, whether it is pure, or how it handles invalid or empty input.

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 brief and front-loaded with the main verb and object. Both sentences provide relevant information with no obvious fluff.

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 nine optional parameters, no required fields, and no output schema, the description is far from complete. It does not explain what output to expect, what 'safe' means, which parameter is central, or how to handle cases where multiple parameters are supplied.

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?

Although every schema parameter has a description, most of those descriptions are unrelated to the stated purpose of checking a file path (e.g., 'IANA timezone name', 'HTTPS URL to normalize or cite'). The parameter schema appears copied from other tools, and the top-level description does not clarify which parameter should actually be passed.

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 phrase 'Check whether a path looks safe' identifies the general resource and action, and 'No disk access' clarifies it is a syntactic/shape check rather than a filesystem stat. However, 'looks safe' is vague and the schema includes many unrelated parameters (url, city, zone, etc.), which muddies the intended scope.

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 gives no guidance on when to use this tool versus sibling validators like browser-url-ok, domain-shape, or github-repo-shape. It also does not mention whether it should be used to validate local paths, reject traversal patterns, or something else.

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