convert_to_email_html

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

Annotations declare idempotent/non-destructive, but description adds crucial output characteristics: 'all styles inlined', 'responsive email table layout', and specific client compatibility. Explains the 'email-safe' HTML generation behavior that annotations cannot capture.

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?

Four sentences, zero waste. Front-loaded with core function (conversion + inlining). Each subsequent sentence adds distinct value: client compatibility, CSS constraints, layout structure. No filler or redundant restatements.

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?

Strong coverage for a conversion tool. Despite no output schema, description characterizes the HTML output sufficiently (inlined styles, table layout, client compatibility). Schema handles parameter mechanics. Minor gap: doesn't mention the dual return modes (string vs file summary), though schema covers this.

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%, providing excellent parameter documentation (markdown format support, output_path behavior). Description references no parameters specifically, relying entirely on schema—a valid pattern when schema coverage is comprehensive. Baseline score applicable.

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?

Excellent specificity: verb 'Convert' + source resource 'Markdown' + target 'email-optimized HTML'. Critically distinguishes from sibling 'convert_to_html' via 'email-optimized' qualifier and specific compatibility claims (Outlook, Gmail, Apple Mail).

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?

Clear contextual signals for when to use: 'email-optimized', 'compatible with Outlook, Gmail...', and 'no external CSS dependencies' clearly indicate this is for email delivery vs web publishing. Lacks explicit sibling comparison (e.g., 'use convert_to_html for web pages'), but usage context is unambiguous.

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