convert_html_to_pdf

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

Discloses temporary URL duration (~1 hour), cost (50 sats), and payment flow (requires create_payment). No contradictions with missing annotations.

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?

5 sentences, each serves purpose, but could be slightly tighter. Information is front-loaded with core action.

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?

Covers output format, use cases, payment, sibling comparison, and technical requirements. No gaps for a conversion tool.

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 covers all parameters; description adds context for format parameter (set to 'markdown' for Markdown) and explains paymentId in context. Adds value beyond schema.

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?

Clearly states it converts HTML or Markdown to PDF, with specific output format (JSON with temporary URL). Differentiates from sibling convert_file.

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?

Explicitly suggests use cases (invoices, reports, etc.) and directs to convert_file for file conversion. Also mentions payment requirement and setup.

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