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

With no annotations, the description fully carries the disclosure burden. It reveals the paid nature, exact cost, recipient, finality/no-refunds, HTTP 402 gating, relay arrangement, single-fetch limitation, and that page content is not stored. This is far richer behavioral context than most tool descriptions provide.

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?

The description is repetitive and heavily padded with billing language: the cost appears twice and 'payments are final/no refunds' appears twice. The core functional sentence is buried inside an untrusted-provider content block after a lengthy payment warning, so it is not front-loaded or tightly structured.

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 one-parameter tool with no output schema and no annotations, the description covers the essential operational context: return fields, single-fetch behavior, no content storage, and payment/402 behavior. It is not fully complete because it does not explain how a payment should actually be presented or describe the response shape beyond field names.

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 coverage is 100% and the schema already describes 'url' as 'A public http(s) URL.' The description adds that only one URL is fetched and that it must be public, but it does not provide meaningful new parameter-level semantics beyond the schema. Baseline 3 is appropriate.

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 clearly states a specific verb and resource: 'Fetches one public URL you supply and returns its title, description, canonical URL and OpenGraph tags.' It also adds a sharp boundary with 'Single fetch only — it does not crawl, follow links, or store page content,' which distinguishes it from broader scraping behavior. The tool name and listing agree on the exact function.

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?

The description gives explicit when-not-to-use context: it is a single-fetch tool that does not crawl, follow links, or store page content. That tells an agent this is not the choice for multi-page or bulk scraping. It stops short of 5 because it does not name a specific sibling/alternative to route to when those broader behaviors are needed.

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