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

No annotations are provided, so the description must carry the behavioral burden. It mentions a payment model ('5 free trial calls per signed wallet'), which is useful context about cost/auth. However, it omits whether the operation is read-only, the conversion direction, and any limits or side effects.

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 very short—a single line with a noun phrase and a pricing tag. It's concise but not front-loaded with a clear action, and the pricing emoji may distract. Still, it fits in a compact form.

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 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the conversion behavior, required parameters (none are required per schema), or how 'md', 'text', 'input', and 'format' interact. The payment note is the only added value, but core usage details are 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 100%, so the parameters are already documented in the schema (though generically: 'Md to process', 'Text to process', etc.). The description adds no parameter meaning beyond what the schema provides. Baseline 3 applies.

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 'Markdown to text or HTML', which conveys a conversion direction, but it's ambiguous—the name suggests markdown-to-something, yet the schema contains 'md' and 'text' parameters, hinting at bidirectional conversion. Without a clarifying verb like 'convert' and explicit source/target, the purpose is vague.

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?

There's no guidance on when to use this tool versus alternatives like x402-markdown-html or x402-text-toolkit. The only additional info is a pricing note about free trial calls, which doesn't help selection.

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