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

Adds context the annotations don't carry: the operation is BILLED, the return is a { FileUrl } valid ~24h, and TOC support is engine-specific. It doesn't clarify what destructiveHint=true means for a render (file creation/overwrite/billing), but that is a minor gap against a real safety hint already present.

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?

Three dense sentences, front-loaded with the engine and its differentiator, then return value, billing, and endpoint. No filler; each clause carries distinct information.

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 an 8-parameter, nested-object tool with no output schema, it covers engine choice, output shape/lifetime, and billing. Storage/useCustomStorage and inline/attachment behavior are left entirely to the (100%-covered) schema, which is acceptable but slightly incomplete for a billed write operation.

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 coverage is 100%, so baseline is 3, but the description goes beyond the schema's generic 'engine-specific options' passthrough by naming concrete keys (enableToc / tocOptions inside `options`). That is genuine added meaning for the one non-obvious parameter.

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?

States a specific verb (render), resource (HTML string to PDF) and the engine (wkhtmltopdf), then positions it against the sibling Chrome path by name ('an alternate to Chrome'). An agent can distinguish it from api2pdf_html_to_pdf without opening either schema.

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?

Gives clear selection context: this engine is the one that supports a table of contents, implying 'use this when you need a TOC.' It does not explicitly state when to prefer the Chrome sibling instead or name it, so it stops short of full routing guidance.

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