generate_pdf

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing behavior like error handling, timeouts, authentication needs, or side effects. For a tool with 18 parameters and no output schema, this is insufficient.

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 extremely concise (one sentence, 13 words) with no wasted words. It front-loads the core purpose and key constraint, making it easy for an agent to quickly grasp the tool's function.

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's complexity (18 parameters, no output schema, many siblings), the description is too brief. It doesn't explain the output format, how to combine parameters, or provide an overview. The agent would lack information to use the tool effectively beyond basic usage.

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 high (94%), so the schema already documents most parameters. The description adds value by highlighting the mutual exclusivity of url and html, which is not enforced in the schema. However, it does not elaborate on other parameters or their interactions.

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 clearly states the tool generates a PDF from a URL or raw HTML, specifying the two primary inputs and the mutual exclusivity constraint. This distinguishes it from sibling tools like flatten_pdf or protect_pdf, which perform different PDF operations.

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 basic guidance on parameter selection ('Provide either url or html, not both') but lacks information on when to use this tool versus alternatives like upload_pdf or get_document. No explicit when-not or context for choosing among siblings.

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