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

With no annotations, the description carries the full burden and does disclose real behavioral traits beyond the schema: server-side execution, SSRF guarding with redirects re-validated, a 10s timeout, a 1MB cap, and per-call cost ($0.02 USDC on eip155:8453). It stops short of stating auth/credential requirements, whether JavaScript-rendered content is captured, or the failure/truncation behavior when the 1MB cap is hit.

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?

Four sentences, front-loaded with the core verb/resource and output format, followed by constraints and cost in descending priority. Mild waste exists in the promo-style line ('The reader pattern agents use to actually understand web pages') and in the final sentence restating the purpose already given in sentence one.

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 two-parameter tool with no output schema and no annotations, the description covers what is returned (markdown), the operational envelope (timeout, size cap, SSRF re-validation) and pricing, which is enough for an agent to call it correctly. Gaps remain around error behavior, JS-rendered pages, and truncation semantics, but nothing critical to invoking it 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?

Both parameters already have schema entries and schema description coverage is 100%, so the baseline is 3. The description adds no parameter-level meaning: it never explains that maxChars truncates the returned markdown, nor how it interacts with the stated 1MB fetch cap, nor any default. The 'url' semantics are also not clarified (scheme restrictions, whether localhost is rejected).

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 ('Fetch a web page server-side and convert it to clean markdown') and enumerates the output shape (headings, links, lists, tables) and what is stripped (scripts, styles, boilerplate). This distinguishes it from near-siblings like dev_readability, dev_scrape_selector and dev_page_verify, which operate on pages but return scores, selected fragments, or verdicts rather than clean markdown.

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?

Gives an explicit when-to-use trigger ('Use this when an agent needs to fetch any page and get clean markdown an LLM can read'), which is actionable context. However, it offers no exclusions or named alternatives (e.g., when to prefer dev_scrape_selector for a specific CSS target or dev_pdf_to_text for PDFs), so routing among page-oriented siblings is still 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.