generate_pdf_from_html

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

No annotations present. The description only states the return format (Base64-encoded PDF bytes). Lacks disclosure on idempotency, safety (read/write), authentication needs, size limits, or any side effects.

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?

Concise two-line description with structured Args/Returns. No wasted words, though it could be more informative about constraints.

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?

Tool is simple with one param and an output schema. Description covers input and output format. However, context signals indicate no nested objects or enums, so basic completeness is adequate, but missing details like supported HTML features or file size limits.

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?

One parameter 'html' described as 'HTML content to convert to PDF'. This adds context beyond the schema's type string. Schema description coverage is 0%, so description partially compensates.

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 verb 'Generate' and resource 'PDF from HTML content'. Distinguishes from siblings implicitly by specifying HTML input, but lacks explicit differentiation from similar tools like 'generate_pdf_from_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 'generate_pdf_from_markdown' or 'fill_pdf_form'. No exclusions or prerequisites mentioned.

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