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

Annotations already cover read-only and open-world behavior, but the description adds valuable operational context: it runs a real headless browser, blocks private addresses, does not charge for failures, costs $0.02 in USDC via x402 or prepaid credits, and is available in the free trial. This is well beyond what the structured fields 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 front-loaded with the core purpose and efficiently packs in return values, alternative tool routing, restrictions, and pricing. The only minor redundancy is that the $0.02 price appears in both the title and the description.

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 an output schema and rich annotations, the description covers what the tool does, when to use it versus the cheaper alternative, restrictions, billing behavior, and availability. Nothing important for correct invocation is missing.

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% for the single url parameter, and the schema already says it must be a public web page address. The description reinforces that private addresses are blocked, but adds little parameter-level meaning beyond the schema baseline.

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 specific verb and resource: reads JavaScript-heavy web pages and returns clean Markdown. It explicitly distinguishes itself from the sibling /markdown tool for ordinary pages and PDFs, so an agent can choose without opening both schemas.

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?

Explicitly says to use /markdown for ordinary pages and PDFs (cheaper), framing this tool's niche as JavaScript-heavy pages such as SPAs, React/Vue sites, and dashboards. It also notes that private addresses are blocked, giving clear boundaries for when the call will succeed.

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