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

Annotations only supply destructiveHint=true, a lower bar, and the description adds genuinely useful behavior the annotation cannot convey: the return is a FileUrl with a ~24h validity window and the call is BILLED (consumes credits). It still omits what 'destructive' means here, rate limits, or credit cost magnitude, so it is strong but not exhaustive.

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 short sentences, front-loaded with the action, then the return value, then the billing flag and endpoint. No filler; each sentence 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?

With no output schema, the description takes on the burden of describing the return and does so ({ FileUrl }, ~24h expiry), plus it discloses billing. It does not touch the options passthrough or output_binary alternative, but those are covered in the schema, so the gap is minor.

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 all 8 parameters (including nested options/storage) are already documented in the schema, establishing the baseline of 3. The description adds no parameter-level detail beyond the schema, so no credit above baseline is warranted.

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 and resource ('Render a Markdown string to a PDF using headless Chrome') and names the engine, which cleanly separates it from siblings like html_to_pdf, url_to_pdf and wkhtml_to_pdf. An agent can identify the input type and output type without opening the 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?

The description implies usage (a Markdown source string is required) and flags the billing cost, but never states when to pick this over html_to_pdf/wkhtml_to_pdf/url_to_pdf. No exclusions or prerequisites are given, so routing between the Chrome/WKHTML/URL PDF variants is left to inference.

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