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

The description explicitly notes 'No disk access', but it does not disclose other behavioral aspects such as return values, side effects, or failure modes. Without annotations, this is partial transparency.

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, focused sentence with no unnecessary words, meeting the highest standard of conciseness.

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 tool's schema exposes nine parameters but the description gives no rationale for the extraneous ones or any usage context, leaving the agent without necessary information to correctly invoke the 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?

Although schema coverage is 100%, most parameter descriptions (ref, url, city, feed, host, json, zone, query) are irrelevant to the stated purpose of checking path safety. Only 'path' aligns with the tool's function, and the others actively confuse rather than clarify.

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 clearly states the tool's function (checking path safety) and its non-disk-access behavior, making the purpose unambiguous even without sibling context.

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 provides no guidance on when to use this tool versus the many sibling tools (e.g., browser-url-ok, fetch-status, normalize-url), leaving the agent to infer applicability.

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