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

The description discloses that there is no disk access, which is a meaningful behavioral trait. However, with no annotations provided, the description carries the full burden of behavioral disclosure. It does not explain what 'safe' means, what the tool returns, or how the additional schema parameters are handled (ignored or also checked), leaving significant ambiguity.

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, extremely concise and front-loaded. It conveys the core action immediately. However, it is arguably under-specified given the tool's complexity, so while efficient, it sacrifices necessary detail for brevity.

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?

Given the tool has 9 parameters, no output schema, and no annotations, the description is insufficient. It addresses only the path parameter's purpose, leaving the function of the other parameters unexplained. The return behavior and usage context are entirely missing, making it incomplete for an agent to reliably invoke the tool 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%, so each parameter has a description. The tool description adds minimal value beyond the schema, only reinforcing the 'no disk access' note for the path parameter. It does not clarify how the other parameters relate to the tool's purpose, so it neither compensates for gaps nor introduces new meaning.

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 and resource: 'Check whether a path looks safe.' This aligns with the 'path' parameter. However, the schema includes 8 other unrelated parameters (url, city, feed, host, json, zone, query, ref) with no mention in the description, making the tool's overall purpose ambiguous and not clearly distinguished from sibling tools like browser-url-ok or validate-json.

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 gives no guidance on when to use this tool versus alternatives. It does not mention conditions like 'use for file path validation' or exclude use for URL checks. No comparison with siblings is provided, leaving the agent to infer usage from the name alone.

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