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

With no annotations, the description carries the full burden and delivers substantial operational detail: SSRF guard, blocked private networks, 10s timeout, 1MB cap, and per-call pricing ($0.003 USDC on eip155:8453). It stops short of describing failure/redirect behavior or what the response payload looks like, which a metadata extractor benefits from.

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 what is extracted before the constraint and pricing fragments. Slightly dense with the em-dash pricing clause, but no sentence is wasted.

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?

No output schema exists, so the description correctly enumerates the returned fields, and it covers the safety/limits that annotations would otherwise carry. Missing cost-on-failure and error-surface details keep it from being fully complete for a paid network tool.

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?

Only one parameter (url) and schema description coverage is 100%, so the schema already fully documents it; the established baseline for high-coverage schemas is 3. The description adds no extra meaning such as accepted schemes (http/https) or handling of redirects/relative URLs.

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?

States a concrete verb (fetch server-side) plus the exact resource extracted (title, meta description, Open Graph/Twitter tags, canonical URL, favicon) and the intent (preview or classify a link). This clearly separates it from content-reading siblings like dev_url_reader.

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?

Gives clear context for use ('the data agents need to preview or classify a link'), but never names an alternative or an exclusion condition, even though the sibling set contains dev_url_reader, dev_url_parser, and dev_feed_parser that overlap in the URL domain. The usage cue is clear but not routing-grade.

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