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

No annotations are provided, so the description bears the full behavioral burden, yet it only says 'value discarded' without explaining side effects, permissions, response shape, or error behavior. For a tool that accepts nine different input kinds this is severely under-disclosed.

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?

It is short, but not concise in the useful sense: it is a single under-specified fragment rather than a front-loaded sentence. Brevity here comes at the cost of meaning, not from efficiency.

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?

With nine optional parameters, no output schema, and no annotations, the description should carry substantial explanatory weight, but it provides essentially nothing an agent needs to invoke the tool correctly. It is wholly inadequate for the tool's apparent complexity.

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% – all nine parameters (ref, url, city, feed, host, json, path, zone, query) are documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline score of 3 applies.

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 'Forwarded by= hop count, value discarded' is a cryptic fragment that never states a clear verb and resource. It hints at hop-count behavior, but an agent cannot determine what the tool actually does from this text, and it does nothing to distinguish it from the many '*‑shape'/'*-ok' siblings.

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 indication of when to use this tool, when not to, or which sibling it replaces. Given the large family of near-identical validators (browser-url-ok, domain-shape, validate-json, etc.), the absence of routing guidance is a serious omission.

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