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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely valuable non-structured context: the rendering pipeline (headless browser + LLM) and, importantly, the per-call price of $0.009 USDC via x402. Auth/payment mechanics and failure modes (e.g., unrenderable pages) are not covered, keeping it short of a 5.

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 tight sentences, front-loaded with the action and resource, then the input contract, then the cost. Every clause carries information; nothing is padding.

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 3-param tool with no output schema, the description covers input modes, mechanism, and pricing, and states the output is structured JSON matching the supplied schema. It leaves the return shape on partial extraction failures implicit, but is otherwise sufficient to invoke correctly.

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 67% and the description adds meaning by framing prompt and schema as mutually alternative ways to describe the target fields ('give a URL plus a JSON schema OR a plain-English prompt'). It doesn't clarify what a missing/partial schema match returns, but the parameter intent is clearer than the schema alone.

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+resource ('Extract structured JSON from any web page') and implicitly separates itself from nearby siblings like scrape/html_tables/ocr by naming the mechanism (headless browser render + LLM schema filling). An agent can tell what this produces without opening the 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?

Explains the two input modes clearly — supply a URL plus either a JSON schema or a plain-English prompt — which is real selection guidance. It does not, however, tell the agent when to prefer this over siblings such as scrape, crawl, or html_tables, so the routing decision is left partly to inference.

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