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

No annotations are provided, so the description carries the full behavioral burden and delivers almost nothing. It does not say whether output is a full HTML document or a fragment, whether the HTML is sanitized, what happens with embedded raw HTML, or what errors look like. Only the one-way direction of the transform is conveyed.

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 single sentence is front-loaded and free of padding, but its brevity comes from omission rather than economy. It is efficient yet too thin to actually guide invocation.

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 no output schema, no annotations, and zero parameter documentation, the description needed to compensate and does not. Key facts an agent needs, such as output shape and the semantics of the gfm/breaks defaults, are missing entirely.

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% across all three parameters, and the description adds no parameter meaning whatsoever. The `gfm` and `breaks` flags in particular are non-obvious and are left completely unexplained, so the agent cannot reason about their effect on output.

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 a clear verb+resource pair ('Convert Markdown to HTML'), but it is essentially a restatement of the tool name and gives no differentiation from nearby siblings such as markdown_format, markdown_preview, or html_format. An agent can infer the transformation, yet cannot tell from this text why it would choose this tool over markdown_preview.

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 is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives. With markdown_format and markdown_preview as siblings, the absence of any distinction leaves selection entirely to the agent's guesswork.

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