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

Beyond readOnlyHint/openWorldHint it discloses stripping behavior (scripts, styles, nav, footer, ads), the security posture (SSRF and redirect protected), an output-size ceiling, and pricing including 'empty results free' — real operational context an agent can't get from annotations. It omits truncation semantics and failure modes (paywalls, robots blocks), so not a 5.

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?

Three short sentences with the conversion purpose front-loaded, then what is removed, then guardrails and cost. Every clause carries information; no filler or restated title.

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?

With an output schema present it correctly avoids describing return structure, and it covers the decision-relevant extras an agent needs: input restriction (public), sanitization, SSRF protection, size limit, and cost. Nothing material for correct invocation is missing.

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 description coverage is 0%, so the description must carry parameter meaning; it states 'max_chars 1–100000 (default 15000)', but those bounds and default are already encoded in the JSON schema, so this mostly repeats structured data rather than explaining what gets truncated or how. The url parameter's semantics are only implied by 'public web page'.

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?

Specific verb+resource ('Convert a public web page to clean LLM-ready Markdown') with the exact output payload named (title, meta description, token count). No sibling tool in the list performs content conversion, so the tool is unambiguous against its neighbors.

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 phrase 'public web page' implicitly excludes authenticated/private targets and the SSRF/redirect note reinforces that boundary, giving clear invocation context. It stops short of an explicit when-to-use/when-not statement or naming an alternative for non-public or non-HTML sources.

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