generate_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively reveals key traits: the tool performs a conversion (implying mutation), returns a PDF file, and includes a cost detail ('$0.03 USDC via x402'), which is crucial for financial awareness. However, it lacks information on error handling, rate limits, or authentication needs.

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 extremely concise and front-loaded, with two sentences that efficiently convey the core functionality and cost without any wasted words. Each sentence adds critical value, making it easy for an agent to parse quickly.

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 the tool's moderate complexity (conversion with a cost), no annotations, and no output schema, the description is partially complete. It covers the basic operation and cost but omits details like response format, error cases, or prerequisites, leaving gaps that could hinder effective tool invocation.

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 description coverage is 100%, so the schema already documents both parameters ('html' and 'format') thoroughly. The description adds no additional semantic details beyond what the schema provides, such as HTML formatting requirements or PDF quality options, resulting in a baseline score of 3.

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 clearly states the specific action ('Convert HTML content to PDF document') and the resource ('PDF file'), making the purpose immediately apparent. It distinguishes this tool from siblings like 'take_screenshot' or 'generate_qr_code' by focusing on HTML-to-PDF conversion rather than other document or image generation tasks.

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?

The description provides no guidance on when to use this tool versus alternatives. While it mentions a cost, it does not specify scenarios where this tool is preferred over other document generation tools or when it should be avoided, leaving the agent without contextual usage instructions.

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