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

With no annotations, the description carries the full burden. It does disclose 'No disk access,' which is a useful safety trait, but it fails to disclose that most other parameters are validated or discarded after a shape check. The description gives no indication that the tool accepts URLs, JSON, timezones, or search text, making the actual behavior opaque and inconsistent with the schema.

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 in length but not in substance. For a tool with 9 parameters and no output schema, it is severely under-specified. The brevity does not serve the agent because it omits critical scope information and leaves the other parameters unexplained.

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's complexity (9 optional parameters, no output schema, no annotations), the description is woefully incomplete. It covers only one parameter and provides no context on how the other parameters behave, what the return value looks like, or how this tool relates to its many siblings. An agent cannot safely call this tool for any input other than a path without risking misinterpretation.

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 already has a clear description. However, the tool description adds no meaning beyond the path parameter (and even repeats 'no disk access' already in the schema). It ignores the other 8 parameters entirely, creating a mismatch between the description and the actual parameter set. The description fails to compensate for the schema's breadth.

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 path safety) and resource (path), and even notes no disk access. However, it only addresses the path parameter while the input schema exposes 8 other unrelated parameters (url, city, feed, json, zone, etc.), implying a broader multi-type validator. The purpose is clear for path but incomplete and potentially misleading 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?

No guidance is provided on when to use this tool versus siblings like browser-url-ok or domain-shape. There is no mention of alternatives, conditions, or exclusions. An agent is left to infer usage from the name and schema alone.

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