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

Goes beyond the annotations by disclosing that raw HTML in the input is escaped and the result is safe to embed — a security trait nowhere in the structured fields — and explains the non-idempotent hint by noting each call is charged so repeats are not free. It still doesn't describe the return shape (fragment vs. full document) or size limits.

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 core purpose and the feature list are front-loaded in the first sentence, with safety and cost after. The billing sentence is dense and the inline example is clumsily formatted inside a prose sentence, costing some readability without padding the whole.

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 one-parameter, read-only tool with full schema coverage and annotations covering safety, this is nearly complete: purpose, supported syntax, escaping behavior, and pricing are all present. Only the exact form of the returned HTML and any input-size limits are left unstated.

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 coverage is 100% for the single 'markdown' parameter, so the baseline is 3. The example ('markdown=# Title ...') illustrates an accepted value but adds nothing about limits, size caps, or encoding that the schema doesn't already cover.

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 both source and target formats ('Convert Markdown ... to HTML') and enumerates the constructs handled, which lets an agent distinguish it from inverse tools like html_to_text or csv_to_markdown without opening the schema.

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?

'Use to publish agent-written Markdown on a web page' gives a concrete usage context, and the cost note implies when not to call it redundantly. However, it never names an alternative (e.g. html_to_text for the reverse direction) or any exclusion, so it stops short of explicit routing.

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