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 limits: no auth, no paywall bypass, no JS execution, and a 2 MB HTML ceiling. It stops short of describing failure/error behavior for blocked or oversized pages, but the operational envelope is clearly communicated.

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 tight sentences, zero filler: the first states the transformation and output shape, the second front-loads the constraints that determine whether the call will succeed. Nothing 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?

For a single-parameter, no-output-schema utility tool, this is complete: the description substitutes for a return-value spec by enumerating the Markdown elements produced (title, headings, lists, tables, absolute links) and covers the operational limits that could cause a failed call.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents 'url' as a public http/https URL. The description reinforces the 'public' constraint but adds no syntax or format detail beyond the schema, matching the baseline of 3.

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 HTML page as clean Markdown') and enumerates the converted structure (title, headings, lists, tables, absolute links). The sibling tools (find_data, get_transcript, make_qr, resume_gap) are unrelated, so no further differentiation is required for an agent to select this tool.

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?

The scope constraints ('public', 'No logins, paywalls or JavaScript rendering') effectively define when the tool will and won't work, which is strong implicit usage guidance. However, it names no alternative tool for dynamic/authenticated pages, so the routing half of the guidance is absent.

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