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

With no annotations provided, the description carries the full burden. It discloses 'No disk access' but does not explain what 'safe' means, what the return value looks like (boolean, error, etc.), or that most input parameters are ignored after a shape check. These are significant behavioral gaps.

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 sentence, which is concise and front-loaded with the primary action. However, given the tool's complex nine-parameter schema and lack of annotation context, the brevity sacrifices necessary detail and comes across as under-specification rather than effective 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 description is incomplete for the tool's context: no output schema, no annotations, and many sibling tools. It does not explain the return type, usage scenarios, or how to handle the non-path parameters, leaving an agent without enough information to call it correctly.

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 has a description, but the tool description adds no meaning beyond repeating 'path' and 'no disk access'. It fails to clarify that only the 'path' parameter is actually used and that the other eight are discarded, which is critical for an agent deciding what to populate.

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 verb ('Check') and resource ('path'), and adds a behavioral note ('No disk access') that distinguishes it from disk-touching tools. However, it does not clarify that only the 'path' parameter is relevant given the schema exposes nine unrelated parameters, which could mislead an agent about the tool's actual 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 on when to use this tool versus the many shape-checking siblings (e.g., browser-url-ok, domain-shape). The description neither mentions exclusions nor conditions that would route an agent here, leaving the choice ambiguous.

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