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

With no annotations provided, the description must carry the behavioral burden. It does disclose 'No disk access,' which is a useful guarantee, but it says nothing about return values, error behavior, or what 'safe' means. For a safety-checking tool this is an incomplete picture.

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 two short, front-loaded sentences with no filler. Every word contributes, though the second sentence could be more useful than simply restating the parameter description.

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?

For a tool with nine optional parameters, no output schema, and no annotations, the description is too sparse. It leaves the agent unsure of what to pass, what response shape to expect, and what 'safe' means—critical gaps for a validation tool.

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 coverage is 100%, so each parameter is already documented. However, the parameter list includes nine unrelated options, and the description does nothing to clarify which parameter should be supplied; it implies 'path' without tying it to the actual schema structure.

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 specific action ('Check') and resource ('path') and adds a key constraint ('looks safe', 'No disk access'). This distinguishes it from the many sibling 'ok' and 'shape' tools, though it leaves the exact meaning of 'safe' to inference.

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 does not explain when to use this tool over siblings like browser-url-ok or github-url-shape, nor does it mention prerequisites or exclusions. It says only what it does, not when to choose it.

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