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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the return format (markdown) and the fallback routing, but says nothing about paywalls/blocks, credit cost of premium or challenge_mode, or what happens on failure — all of that lives only in schema field descriptions.

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?

Three short sentences with the core capability front-loaded and routing details packed tightly into the second sentence. 'Required: url' is the one wasted clause since the schema already marks it required.

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?

Five parameters, 100% schema coverage, no output schema — the description correctly tells the agent what comes back (markdown) and which sibling to pick instead. The only gap is that cost implications of premium/challenge_mode are left entirely to the schema.

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 every parameter (url, premium, max_chars, render_js, challenge_mode) is already documented with defaults and credit costs. The description adds only 'Required: url', which merely restates the schema's required list, so the 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 ('Read one public URL as markdown') plus the output format, which is the key fact an agent needs. It also names the sibling tools it is not (google_search, and the Amazon/eBay/Zillow domain tools), so it is distinguishable 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?

Explicit routing: use for a known page, not discovery (google_search), not marketplace/real-estate data (their tools), and not for raw HTML/links/summaries (REST scrape). Both when-to-use and when-not-to-use are stated with the alternative named in each case.

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