Render local Markdown to HTML

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

Beyond the annotations, the description discloses important behavior: it writes a new standalone HTML file, applies a restrictive CSP, verifies tag nesting and source text, keeps links clickable but never opens them, and makes no network requests. This is unusually rich behavioral context for a write-oriented local tool.

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 front-loaded with the core render operation and then adds security, supported syntax, and link behavior without filler. Every sentence contributes useful scope or behavior information.

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 two-path local file conversion tool with full schema coverage and annotations, the description covers supported syntax, security posture, link handling, and browser requirements well. It does not mention overwrite behavior for an existing output_path or error/return behavior, which leaves a minor 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?

Schema coverage is 100%, so both required path parameters are fully documented by the schema. The description adds only the implication that output_path receives a new standalone HTML file and does not explain path handling beyond what the schema already states.

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 specific verb and resource: render a Markdown dialect into a new standalone HTML file. It also scopes the output with a restrictive CSP and distinguishes the tool from browser-based rendering and raw HTML handling.

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?

It gives clear usage context by listing supported Markdown features and explicit exclusions such as raw HTML, image rendering, automatic requests, and browser use. It does not name a specific alternative sibling tool, so it falls short of full when-to-use/when-not guidance.

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