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

The description discloses that no disk access occurs, but does not explain what the tool returns, how 'safe' is determined, whether it accepts one parameter or many, or what happens on invalid input. With no annotations, these behavioral details are missing.

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, front-loaded sentence with no filler. It communicates the core action and a key safety constraint efficiently.

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?

Given the complex 9-parameter schema and absent output schema, the description is incomplete: it does not identify which parameter to supply, what kind of result to expect, or how this tool differs from the sibling shape-checking tools. The 'No disk access' note is useful but insufficient.

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?

Parameter descriptions in the schema provide 100% coverage, so the baseline is met. However, the tool description itself adds no parameter-selection guidance, and several schema descriptions ('Git ref name', 'City name for a public weather hint') feel disconnected from a file-path safety check.

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 object ('check whether a path looks safe') but the input schema exposes 9 unrelated optional parameters (ref, url, city, feed, host, json, zone, query) with no indication of how they relate to a path check. The purpose becomes ambiguous because the schema contradicts the apparent narrow 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?

There is no guidance about when to use this tool versus the many sibling shape/validation tools, nor any mention of required input or invocation pattern. The only additional note ('No disk access') is a safety property, not a usage condition.

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