Markdown to HTML

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

Annotations already indicate idempotentHint=true and no destructive/readOnly concerns. Description adds value by specifying 'produces standalone HTML with CSS styling' and 'printable as PDF via browser', which are behavioral traits not captured by annotations. No contradictions.

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?

Description is very concise with a single line plus an argument list. Front-loaded with main action and key output detail. Every sentence adds value: conversion purpose, arguments, output format and use case.

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?

The tool has 3 parameters, no output schema, and moderate complexity. Description adequately covers inputs and output format, but lacks details on error handling, encoding, or behavior for invalid inputs. Given the simplicity, it is mostly sufficient but could be more complete.

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% but descriptions are brief ('Markdown file', 'HTML output', 'Document title'). Description adds context by grouping parameters and noting the optional title. Provides additional meaning beyond schema for input_path and output_path by linking to the conversion process.

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?

Description clearly states verb 'Converts' and resource 'Markdown to formatted HTML'. Explicitly distinguishes from sibling 'cc_md_to_pdf' by noting HTML can be printed as PDF via browser, implying this tool is for HTML conversion while the sibling directly produces PDF.

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?

Description provides clear context: converts markdown to HTML with CSS styling for PDF printing. However, it does not explicitly state when to use this over cc_md_to_pdf or when not to use it, missing a clear alternative exclusion.

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