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

No annotations are provided, so the description carries the full behavioral burden. It does well on scope of content returned, but says nothing about the fetch itself: whether the remote page is actually contacted, expected latency, redirect handling, or behavior on unreachable/non-HTML URLs. Output schema covers the return shape, but the network-fetch traits an agent needs are undisclosed.

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 output scope and followed by uses; no filler. The field enumeration partially overlaps with the existing output schema, but it still helps the agent judge fit before invoking, so it earns its place.

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 an output schema present, the description is not obliged to explain return values, and it correctly focuses on purpose and use cases. The remaining gap is fetch behavior (network dependency, failure modes) for a tool with zero annotation coverage, which keeps it from a 5.

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% for the single `url` parameter, so the description must compensate and only weakly does: 'a web page' implies an http/https URL but gives no format, scheme requirement, or handling of redirects/shortened links (expand_url exists as a sibling). Enough to call it, not enough to call it well.

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 resource and output scope ('Link-preview metadata of a web page') and enumerates the exact fields returned (title, OG/Twitter image, canonical URL, favicon, RSS). The closing clause 'without reading the full page' cleanly separates it from the sibling read_web_page, so an agent can route between them without opening a schema.

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 gives three concrete usage contexts (link previews, bookmark enrichment, URL classification) and implicitly excludes the full-page-read case handled by read_web_page. It doesn't state explicit exclusions or failure conditions (e.g. non-HTML URLs, unreachable hosts), so it stops short of a 5.

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