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

The description explicitly promises 'No disk access,' which is useful transparency, but it says nothing about return values, error behavior, or what 'safe' means, leaving the tool's behavior largely opaque.

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 with no redundant words; the key statement is front-loaded and the no-disk-access caveat is included.

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?

The description is too sparse for the tool's apparent complexity: no output schema, no safety criteria, no error conditions, and no explanation of the many accepted parameters.

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 path parameter has a clear description, but the input schema includes eight other parameters whose descriptions read as unrelated to path safety (e.g., url, city, feed, zone), and the tool description does not explain whether or how they are used.

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.' However, 'safe' is undefined and no criterion is given, and it doesn't distinguish this from other shape-checking siblings beyond the path focus.

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?

No guidance is provided for when to use this tool versus alternatives like domain-shape or browser-url-ok, nor are prerequisites or intended contexts mentioned.

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