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

Annotations only carry destructiveHint=true, so the description usefully adds the two things an agent most needs: the operation is BILLED and the default result is a FileUrl that expires in ~24h. It does not explain why the annotation marks this render as destructive, leaving one gap.

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, front-loaded sentences: purpose, return behavior, then billing and endpoint. No filler, and cost plus return shape are surfaced where an agent will see them.

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 tool with nested objects and no output schema, the description covers the essentials: what goes in, what comes back, how long it lasts, and that it costs money. The custom-storage path is left entirely to the schema, which is acceptable but not maximally complete.

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%, including full prose for output_binary, so the schema already does the heavy lifting and a 3 is the baseline. The description restates the output_binary/FileUrl tradeoff and lifetime but adds no syntax or format detail not already in the schema.

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 an HTML string to an image') plus the engine ('headless Chrome'). The 'HTML string' scope implicitly separates it from api2pdf_url_to_image, though no sibling is named explicitly, which keeps it just short of a 5.

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 statement of when to use this over api2pdf_html_to_pdf, api2pdf_url_to_image, or api2pdf_wkhtml_to_pdf, and no prerequisites or exclusions. The only guidance-like remark is the recommendation to prefer output_binary:false, which is parameter advice rather than tool-selection guidance.

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