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

Annotations carry only generic safety hints, and the description adds substantial operational context: exact price ($0.005 per call), the settlement rail (USDC on Solana via x402), the two-step challenge/retry protocol with the _meta["x402/payment"] key, and an HTTP fallback endpoint. It stops short of stating output form or error behavior for invalid markdown.

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?

Purpose is front-loaded in the first clause, followed by the payment mechanics needed to actually invoke it. Slightly dense in the x402 parenthetical but every element (price, rail, retry, HTTP mirror) is actionable.

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?

For a single-parameter pure conversion the definition covers purpose, cost, and invocation protocol, which is most of what an agent needs. With no output schema, a note on the returned HTML or on handling unsupported markdown would close the remaining gap.

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?

One optional parameter (text) with 100% nominal coverage, but the schema description is literally "string", so the description is what actually conveys that the value is markdown source. That is minimal added meaning and the 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?

"Convert basic markdown to HTML" states a specific verb and resource, and no sibling in the long devutils_* family competes with it (csv_to_json, json_format, etc. are distinct conversions). "Basic" also scopes the input subset, which an agent would otherwise have no way to infer.

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 explains the payment procedure (call without payment, get the challenge, retry with the payment) but gives no guidance on when to choose this tool versus, say, doing the conversion locally or using pubconvert_convert. Usage is implied by the tool name rather than stated.

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