html_to_pdf

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

Annotations already declare readOnlyHint=true, so no side-effect warning is needed. The description adds the basic input/output behavior ('Send HTML markup and receive a PDF') but does not disclose potential limitations such as CSS support, file-size limits, or binary response handling. It is adequate but not rich.

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 short and front-loaded with the core purpose, followed by relevant use cases. The middle sentence 'Send HTML markup and receive a PDF' is slightly redundant with the first sentence, but the overall structure wastes little space.

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?

For a single-parameter conversion tool with read-only annotations and no output schema, the description conveys enough to get started: what goes in, what comes out, and common examples. It does not describe the exact binary/output format or rendering behavior, but that is a minor gap for such a straightforward 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?

The schema covers the only parameter (html) with a description, and the tool description does not add meaning beyond that. Since schema coverage is 100%, the baseline of 3 is appropriate; there is no additional semantic guidance such as supported HTML subset or escaping requirements.

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 a specific action ('Convert HTML content to a PDF document') with both input and output, so an agent knows what the tool does. It does not distinguish itself from sibling tools like markdown_to_pdf or html_to_markdown, but the verb-resource pairing is unambiguous enough for a 4.

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 phrase 'Useful for generating invoices, reports, and documents' gives general use cases, but there are no explicit when-to-use/when-not-to-use instructions or references to alternatives. This is implied usage guidance, not clear routing.

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