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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new operational context: a paid x402 charge of 0.002 XNO, a stealth-browser execution model, and ~1s latency. It stops short of describing failure modes, pagination, or what happens when payment is declined, so it is strong but not exhaustive.

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 compact sentences, front-loaded with the action and mechanism, followed by output contents, cost, and speed. No sentence is padding; even the payment and latency clauses carry decision-relevant information.

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, return values need not be enumerated, yet the description still summarizes them. Combined with cost, speed, and browser model, an agent has enough to invoke correctly; only edge-case behavior (payment failure, per-page limits) is unaddressed.

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%, so both 'url' and 'elements' are already documented in the schema and the description adds no syntactic or format detail beyond it. The mention of 'interactive elements' loosely mirrors the 'elements' flag, but this is the baseline case where the schema does the heavy lifting.

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 ('Scrape one page'), plus the mechanism ('real stealth browser — no AI'), which implicitly separates it from the AI-driven browser_agent and from the plural scrape_pages sibling. An agent can tell what this does and how it differs without opening any 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?

Usage is implied rather than stated: single-page scope, no AI, ~1s latency, and a fixed cost hint at when to prefer it over an AI agent or bulk scraper. However, no sibling is named and there is no explicit when-not guidance (e.g. use scrape_pages for multiple URLs, browser_agent for interaction).

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