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

Goes well beyond the annotations by disclosing price (0.003 USDC), payment rail (x402 on Base/Solana, no account/API key), failure semantics (invalid input refused before payment, a failed run is never charged), and the PaymentRequired response without payment. It also gives a free-sample path via get_example and the HTTP equivalent.

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?

Capability is front-loaded in the first sentence, then pricing and payment behavior follow. The pricing, sample-call, and HTTP-endpoint sentences are longer than strictly necessary but each carries information an agent needs before invoking a paid tool.

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 no output schema, the description supplies the full list of return fields, and for a paid tool it fully covers cost, payment flow, and failure/charging behavior. Nothing an agent needs in order to call and pay correctly is missing.

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% for the single required `url` parameter, so the schema already carries the semantics. The description adds only that any URL is accepted, not format/validation details, which matches the baseline 3 for a fully documented 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 opens with a specific verb+resource ("Link preview of any URL") and enumerates the returned fields (title, description, Open Graph/Twitter fields, favicon, oEmbed, JSON-LD), so the agent knows exactly what it produces. It does not explicitly contrast with the closest siblings such as web_extract or url_safety_check, which is the only gap.

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?

It states a clear use case ("render rich links or to check how a page will look when shared"), which is a real context signal for selection. It stops short of naming when-not-to-use or pointing to alternatives like web_extract, so it is strong but not exhaustive.

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