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

The description adds substantial behavior beyond the annotations: JavaScript and network access are disabled, only submitted HTML is used, images must be inline data URLs, and the resulting PDF is stored for 24 hours with storage_id and storage_url. These details are exactly what an agent needs to invoke the tool safely and interpret the result.

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 text is front-loaded with the core rendering behavior, then proceeds through options, storage lifetime, retrieval, and auth requirements. Every sentence adds actionable information without padding.

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 nested options object, no output schema, and annotations that leave storage and retrieval behavior unstated, the description is complete enough for correct invocation. It explains the output shape, where the file goes, and how to read it back.

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?

With 0% schema description coverage, the description carries the parameter burden and does so well. It documents the html input constraints (no external network, inline data URLs required) and enumerates the options keys with valid page sizes, orientations, and margin examples such as 10mm.

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 states a specific verb-and-resource pair: render HTML to a PDF. It is immediately distinct from siblings such as process_image or read_stored_file, and the opening sentence leaves no ambiguity about what the tool produces.

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?

It gives clear operational context: no API key or sign-up is needed, the output is stored for 24 hours, and read_stored_file retrieves it. It does not explicitly state when not to use this tool or name an alternative renderer, but the retrieval follow-up and auth guidance are useful usage cues.

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