Convert HTML to PDF

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

Description discloses cost (1 credit on success) and return format (embedded resource), which adds value beyond openWorldHint annotation. However, it does not mention any side effects or constraints like HTML size limits or timeout.

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?

Two sentences with core info: purpose, method (Chromium), optional features, cost, and return type. No wasted words.

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?

Given 18 parameters and no output schema, description covers main purpose but does not clarify what 'embedded resource' means (e.g., base64 encoded) or provide additional context for complex layout options.

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?

All 18 parameters have descriptions in the schema (100% coverage), so the description adds minimal extra meaning beyond 'optional CSS and layout options'. Baseline of 3 is appropriate.

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 it renders HTML to PDF using Chromium, with optional CSS and layout options. This distinguishes it from siblings like convert_file and convert_markdown.

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?

No guidance on when to use this tool versus alternatives like convert_file or convert_markdown. The description does not mention when raw HTML input is appropriate.

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