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

Beyond the readOnly/idempotent hints, the description discloses the free tier, the concrete rate limit (20 reads/minute per IP), the 5 MB payload cap, accepted content types, and the return shape (clean Markdown plus title). That is exactly the operational context the annotations cannot carry.

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 sentences, no waste. 'Free.' is front-loaded and the paid-alternative pointer lands last as a natural fallback, with limits stated inline rather than in a separate paragraph.

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 one-parameter read tool with no output schema, everything needed to call it correctly is present: input constraints, size/rate limits, supported formats, and what comes back. No meaningful gap remains.

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% and the single url parameter is already documented as 'a public http(s) URL'. The description reinforces the public-access constraint and implicitly bounds input to web documents under 5 MB, but adds little beyond that.

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 ('read a public web page or document') and enumerates supported formats and size ceiling, so the agent knows exactly what it returns. It also names the sibling url_to_markdown and states the axis of difference (free vs paid/rate-limited).

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?

Explicitly routes to url_to_markdown when the 20/min limit is insufficient, which is a real when-to-use alternative. It does not address the other plausible alternative, file_to_markdown, for local or already-uploaded files, so routing is clear but not exhaustive.

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