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

Goes well beyond annotations: quantifies the billable cost (5 standard / 25 premium credits), states the confirm:true gate, enumerates unsupported features, warns that content is untrusted website data, and discloses truncation of large results and the absence of automatic retries. It also implicitly explains why readOnlyHint=false despite the read framing — the call consumes credits.

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?

Front-loaded with the most decision-critical fact (billable read + credit cost + confirm gate) in the first two clauses, then constraints and caveats. Six short sentences, none redundant.

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?

No output schema exists, and the description compensates by describing the return (HTML), the truncation behavior, and the trust level of the payload. Combined with the credit/billing disclosure and feature limits, an agent has what it needs to call this correctly and safely.

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 83%, so the schema already documents url, confirm, country, wait_ms and premium_proxies. The description adds no syntax or format detail for any parameter beyond restating the credit cost, so baseline 3 applies.

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: 'Render one public page with JavaScript and return HTML.' The JavaScript-rendering qualifier implicitly distinguishes it from the sibling scrapeowl_scrape_page, but no sibling is named explicitly, so the agent must infer the routing.

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 by 'with JavaScript' (use when rendering is required) and gated by 'Requires confirm:true', but there is no explicit when-to-use/when-not statement naming scrapeowl_scrape_page or scrapeowl_extract_elements as alternatives. The constraints listed (no custom scripts, cookies, headers, forms; no automatic retries) describe capability limits rather than selection guidance.

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