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

With no annotations provided, the description carries the full burden and does so well. It discloses JavaScript execution, output content, stripping behavior, optional API key authentication, rate limits, and pricing. This is rich behavioral context that goes far beyond the schema.

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 compact yet informative: core functionality and the critical JavaScript-execution trait come first, followed by usage context, return shape, and access constraints. The pricing and key information earns its place because it directly affects real-world invocation.

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 tool with no output schema, the description supplies the key return fields, content formatting, and cleanup behavior. Combined with the fully documented schema, the agent has everything needed to invoke the tool correctly and understand what it will receive, including auth and rate-limit constraints.

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%, and the schema already documents url, format, and maxChars with useful details such as defaults and enum meanings. The tool description adds no parameter-specific semantics beyond echoing 'clean text or Markdown,' so the baseline score of 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 states a precise action ('Read a web page as clean text or Markdown, WITH JavaScript executed') and names concrete outputs (title, description, readable content, links) and preprocessing (navigation and cookie banners stripped). This clearly distinguishes it from sibling tools like url_screenshot or url_to_pdf.

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 explicitly tells when to use this tool: when a plain fetch returns an empty shell or loading spinner, with concrete examples like single-page apps and client-side rendered sites. It does not explicitly name alternatives or exclusion criteria, so it stops short of full when/when-not guidance.

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