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

With no annotations available, the description carries the full burden on behavior. It does disclose a meaningful behavioral trait—'Body discarded'—and scopes the tool to public URLs. Still, it omits any statement about the port, error cases, network side effects, or how the non-URL parameters are handled, so transparency is minimal.

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 two short declarative sentences with no filler. Each sentence carries essential information: the core purpose and the fact that the body is discarded, making the description unusually tight and front-loaded.

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 plainly undercompleting for a tool with 9 parameters, no annotations, and no output schema. It does not explain the full parameter acceptance, what is returned per parameter, how to handle errors, or why the other 8 parameters have no mention. It is only a partial snapshot of the tool's actual capability.

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%, which sets a baseline of 3. The description does not add any meaning that the schema doesn't already provide: it does not map explicit parameters to their behavior or disambiguate which parameter is the URL. The tool-level text adds almost nothing beyond the schema.

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 names a specific action ('HTTP status and content type') and a resource ('public URL'), which clearly captures the URL case. However, it does not account for the 9 unrelated schema parameters (e.g., city, json, zone) and does not differentiate against sibling tools like fetch-status or browser-url-ok, leaving the tool's overall purpose ambiguous.

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 its many siblings (fetch-status, browser-url-ok, normalize-url, etc.). There is no explicit context or exclusion, so an agent cannot determine when to select it.

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