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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered without the description. The description does add one behavioral caveat, 'basic subset', warning of limited markdown feature coverage, but omits output format, error behavior, or what 'basic subset' actually excludes.

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?

It is a single short sentence, which is appropriately sized, but it is not well front-loaded and carries noise ('from freedailypro', 'client and server side') that does not help an agent.

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 simple one-parameter conversion tool whose annotations already cover the safety profile, this is minimally adequate. However, the description leaves the input contract and the meaning of 'basic subset' unexplained, which matters given the zero schema coverage.

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?

The single required 'markdown' parameter has 0% schema description coverage; the description never mentions the input at all, so it does not compensate for the gap. Nothing explains the expected string format or constraints on the markdown input.

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 says it's a 'Markdown html converter', which largely restates the tool name rather than elaborating a specific verb+resource+scope. The only added information is the 'basic subset' qualifier, which hints at limited markdown support, but 'client and server side' and the vendor mention add confusion rather than clarity.

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 statement of when to use this tool, when not to, or which sibling to prefer. With many nearby conversion/formatting tools (html_entities, format_json, minify_code), an agent gets no routing guidance at all.

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