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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing: no return shape, no handling of scripts/tables/whitespace, no size limits, no error behavior. The one genuine addition is the pricing/trial constraint, which is useful commercial context but not behavioral.

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?

Very short and front-loaded, but the leading 'x402-html-to-markdown:' merely restates the tool name and the trailing emoji/pricing sentence is boilerplate that does not help invocation. One sentence of real substance plus two filler elements.

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?

The tool is conceptually simple, but with 3 ambiguous parameters, no output schema, and no annotations, the description leaves an agent guessing which input field to populate and what it will receive back. This is under-specified for even a trivial converter.

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?

Three string parameters (`html`, `text`, `input`) sit at 0% schema description coverage and the description never mentions any of them. Worse, the three look like overlapping aliases with zero required field, so the description should explain which to use and whether they are mutually exclusive; it does neither.

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 pair ('Convert HTML to Markdown'), which is unambiguous and lets an agent know exactly what transformation happens. It does not differentiate from the reverse-direction sibling x402-markdown-html or from x402-web2md / x402-strip-html, which are the plausible confusions in this catalog.

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?

No when-to-use guidance, no prerequisites, and no naming of alternatives despite a large sibling set containing multiple HTML/Markdown conversion tools. The only extra sentence is monetization ('5 free trial calls per signed wallet'), which is billing context, not usage guidance.

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