render

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

No annotations are provided, so the description carries the full burden. It discloses that it returns the local output path and mentions a cost of 1 cent, which is helpful. However, it does not mention other behavioral aspects such as authentication requirements, overwrite behavior, or input validation.

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 concise and front-loaded with the core action, and it includes useful cost information. It uses three short sentences without fluff, though it could be slightly more structured to separate behavior from usage.

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 tool has 14 parameters and no output schema, the description is incomplete. It does not explain parameter interactions, defaults beyond the format default, or constraints such as mutual exclusivity of html, markdown, and url. The description is not adequate for an agent to call the tool correctly without inspecting the schema.

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 schema description coverage at 50%, the description does not compensate for the undocumented parameters. It only mentions the input types (HTML, Markdown, URL) but does not explain parameters like format, page_format, landscape, margins, or PNG-specific options. The description adds minimal value beyond 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?

The description explicitly states the tool renders HTML, Markdown, or a URL to a PDF (default) or PNG file, which clearly defines the primary action and output. It distinguishes itself from sibling tools like pdf_merge and pdf_split by focusing on content generation rather than PDF manipulation.

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 provides clear positive use cases (reports, invoices, offers, documentation, screenshots) but does not explicitly mention when not to use it or name alternative tools. It implies usage but lacks exclusions, so it falls short of the top score.

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