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

With no annotations, the description fully carries the burden of behavioral disclosure. It explicitly states it is read-only, polite, honors robots.txt, does not bypass anti-bot measures, and does not support JavaScript-rendered pages. This exceeds typical transparency expectations.

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 a single, coherent paragraph of six sentences. It is mostly efficient but could be slightly more concise by breaking into bullet points. However, it front-loads the main purpose and follows with details, making it easy to parse.

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?

Given the absence of an output schema, the description thoroughly explains the output format (title, description, word count, markdown) and how different inputs are processed (HTML vs plain text). It also covers limitations and behavioral constraints, making the tool's functionality fully understandable without additional documentation.

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?

The schema has 100% coverage with a single parameter 'url' described as 'absolute http(s) URL of a publicly reachable HTML page'. The description adds valuable nuance by explaining that plain text and raw Markdown files are also accepted and passed through, which is not evident from the schema alone. This compensates for any schema brevity.

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 clearly states the tool fetches a publicly reachable URL and returns LLM-ready markdown with title, description, word count, and markdown content. It distinguishes from sibling tools like render_preview and render_screenshot by focusing on text extraction and conversion to 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?

The description provides clear context on when to use this tool: for publicly reachable URLs, especially HTML pages or plain text documents. It mentions limitations like no JavaScript-rendered pages and that it honors robots.txt. However, it does not explicitly name alternative tools for Js-heavy or paywalled content, though siblings like render_screenshot are implied.

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