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

With no annotations, the description carries the burden; the explicit 'No disk access' usefully signals a side-effect-free check. But it omits what the tool returns, what 'safe' includes, and how it behaves on invalid input, so behavioral transparency is only partial.

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?

Two short sentences, no filler, and the key facts are front-loaded. It is concise, though it sacrifices the context needed for parameter selection and clear safety criteria.

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 no annotations, no output schema, and a 9-optional-parameter schema, a two-sentence description is insufficient. It doesn't explain return semantics, the meaning of 'safe,' or why the schema exposes unrelated parameters, so an agent cannot confidently invoke it correctly beyond setting the path field.

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?

The schema itself documents all 9 optional parameters (100% coverage), so the baseline is 3. The description adds nothing about which of the many parameters should be used and even conflicts by mentioning only 'path' while the schema allows ref/url/city/feed/host/json/zone/query; still, the schema text is sufficient for basic parameter meaning.

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 uses a specific verb ('Check') and resource ('path'), and adds the scope 'No disk access,' so an agent can tell it is a static path-shape validator rather than an actual filesystem operation. However, 'looks safe' is not defined, and it does not explicitly differentiate from sibling URL/domain validators beyond the word 'path.'

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 choose this tool over sibling shape-check tools such as browser-url-ok, domain-shape, or jira-key-shape. The only hint is 'No disk access,' which implies a pre-flight shape check, but the description never states a selection condition or alternative.

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