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

The annotations are all false, so the description carries the burden of explaining behavior. It does so well: it reveals that read returns exact bytes with no injected tags or proxied image srcs, that decoding is local and exact, and that any URL can be read without prior visit or fetch. It doesn't discuss rate limits or error cases, but it goes beyond typical 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?

The description is longer than average, but every sentence earns its place. The most important fact — what the tool returns — is front-loaded, and the caveats (exact bytes, local decoding, never re-author from rendered pages) all prevent real mistakes. No filler or repetition of schema content.

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 read tool with a rich input schema and output schema, this description is complete. It covers the tool's purpose, main constraints, when to use it, when not to, and the critical byte-for-byte guarantee. The output schema already documents the return shape, so the description doesn't need to explain it.

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 100%, so the baseline is 3. The description adds meaningful context for the url parameter ('or a bare slug', 'subdomain, cosmetic-prefix and #hash forms all resolve') and clarifies the format parameter's semantic difference ('same bytes both ways'), which is exactly what an agent needs to choose correctly.

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?

The description states a specific action ('Pass an anew.page URL, get back the HTML document encoded in it') and names the resource and the exact output fields. It also disambiguates this tool from the two in-page tools that share the name, which is critical given the ambiguity.

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?

It explicitly says when to use this tool — to read or revise an existing page — and when not to: 'Never re-author from a rendered page, a scraped DOM, or a screenshot'. It also distinguishes the sibling anew_write by explaining that the URL is the source and editing requires read-then-write. This is strong guidance.

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