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

The description itself is unusually informative: 512 KB fetch cap, exact response shape, credit pricing per successful call, and no billing on schema mismatch. However it states the tool fetches arbitrary public web pages, which directly conflicts with the openWorldHint=false annotation; per the rubric that conflict caps this dimension, even though the deeper behavioral detail is strong.

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?

Two sentences, front-loaded with the action and the byte cap, followed by a compact return-field list. The field enumeration is dense but earns its place as a stand-in for the absent output schema; there is no filler.

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 return shape, the truncation flag and the size limit, which is the right compensation. Gaps remain around redirect/timeout behavior and whether JavaScript is rendered, but an agent has enough to call it correctly.

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?

A single parameter fully documented in the schema (pattern, length bounds, refusal of private/loopback/metadata hosts), so the schema carries the semantics. The description still adds the cost model and the truncation behavior that the parameter's value controls.

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 first sentence states a specific verb and resource ('Fetches a public page ... returns its link-preview metadata') and then enumerates the exact payload, which cleanly separates it from sibling fetchers such as web-scrape, page-markdown, web-extract or web-contents.

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?

Usage is only implied by the notion of a 'link preview' plus the schema's restriction to public http(s) URLs; no sibling tool is named and there is no explicit when-to-use/when-not framing (e.g. preview metadata vs. full-page extraction).

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