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

No annotations are supplied, so the description carries full behavioral burden. It does add useful payment/rate context ("5 free trial calls per signed wallet"), which is genuinely beyond the schema, but it omits what a preview does on failure, whether it follows redirects, and whether the call is a safe read-only network fetch.

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 and front-loaded, but the opening "Preview: Preview" duplicates the tool name rather than adding information, and the emoji marketing line consumes a meaningful share of an otherwise tiny description.

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 no annotations, no output schema, and 0% parameter documentation, the definition should explain both inputs and the shape of the result. Only the URL input and three return fields are loosely implied, leaving the "input" parameter and error behavior entirely unspecified.

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 0% across two parameters, so the description must compensate. It implies what "url" means but says nothing about the unexplained "input" parameter, leaving an agent unable to distinguish the two or know what format is expected.

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 uses a specific verb and resource ("Preview a URL") and names the return fields (title, image, description), so an agent can tell it produces link-preview metadata. It falls short of 5 because "Preview: Preview" is redundant and it never contrasts itself with sibling tools like x402-og-tags or x402-meta-tags that also extract page metadata.

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 when-to-use guidance, no exclusions, and no named alternative among the many sibling URL tools (x402-web-retrieve, x402-url-inspect, x402-og-tags). The only contextual hint is the free-trial line, which says nothing about tool selection.

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