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

The only behavioral disclosure is 'No disk access', which is useful but insufficient. With no annotations provided, the description must carry the full burden, yet it omits what happens with the other parameters (e.g., are they validated? discarded?) and whether the tool is read-only or has side effects. The mismatch between the description's singular focus and the schema's breadth is not addressed.

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, concise sentence, which is efficient in word count. However, given the complexity of 9 parameters and the tool's potential multi-purpose nature, the brevity sacrifices critical information, making it under-specified rather than appropriately concise.

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 9 optional parameters, no output schema, and no annotations, this description is far too sparse. It does not explain the overall function across all parameters, what the tool returns, or how the safety check relates to the other inputs. The agent is left with significant uncertainty about how to invoke 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 description coverage is 100% with each parameter having a clear description (e.g., 'Git ref name; discarded after the shape check'), so the baseline is 3. The tool description adds no additional parameter context beyond what the schema already provides, and it does not compensate for the wide parameter variety.

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 whether a path looks safe') and notes 'No disk access', which clarifies the core function for the 'path' parameter. However, the input schema lists 9 unrelated parameters (e.g., ref, url, city, json), making the overall tool purpose ambiguous and failing to differentiate from sibling tools like 'browser-url-ok' or 'domain-shape'.

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 instead of alternatives, nor any context or exclusions. With 27 sibling tools, the lack of routing information leaves the agent to guess the appropriate scenario.

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