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

Beyond the annotations, it discloses the content pipeline, returned fields, scheme/port restrictions, size and timeout limits, robots.txt enforcement, private-address refusal, failure charging behavior, and per-call cost across multiple chains. This is unusually rich behavioral context and does not contradict any annotation.

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 front-loaded with the use case and return value, then layers in constraints and cost. Every sentence carries actionable information, and the dense semicolon-separated limits are still readable.

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 output schema exists, the description need not explain return values, yet it helpfully summarizes them. It also covers permissions-adjacent details (payment, private addresses), failure behavior, and operational limits, making the definition complete for correct invocation.

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 already covers the single URL parameter at 100% coverage, establishing a baseline of 3. The description adds meaningful parameter constraints beyond the schema: only http/https on ports 80 and 443, 5 MB size limit, and 10 s timeout. It does not cover URL encoding or query/fragment handling, so it is not exhaustive.

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 precise verb+resource: returning the readable text of a web page as clean markdown. The resource 'web page' clearly distinguishes it from sibling tools like get_pdf_markdown and get_wiki, even without naming them explicitly.

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 opens with an explicit condition: 'Use when an agent needs the readable text of a web page as markdown.' However, it offers no when-not guidance and does not name alternatives such as get_pdf_markdown for PDF inputs, so it stops short of a full 5.

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