PDF Export for AI Agents

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

Annotations provide hints (readOnlyHint: false, destructiveHint: false, etc.), but the description adds valuable context beyond these: it explains that non-HTML input requires layout creation first, details error-handling behavior ('Read the error message carefully'), and specifies not to use other PDF tools on configuration issues. This enhances transparency without contradicting annotations.

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 front-loaded with the core purpose but includes multiple IMPORTANT notes and error-handling instructions that, while useful, make it somewhat verbose. Each sentence adds value (e.g., layout guidelines, error guidance), but it could be more streamlined for better conciseness.

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 (involving HTML layout and external schema references) and lack of output schema, the description is reasonably complete: it covers purpose, prerequisites, error handling, and references to additional info. However, it doesn't detail output format or success behavior, leaving some gaps in contextual understanding.

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?

The input schema has 0 parameters with 100% coverage, so the description doesn't need to explain parameters. It mentions calling 'pdfcrowd_info' to get the full input schema, which implies parameters exist but are documented elsewhere. This meets the baseline of 3 for high schema coverage without adding parameter details.

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's purpose: 'Export any content (including charts) to PDF' with a specific verb ('Export') and resource ('PDF'). It distinguishes from the sibling tool 'pdfcrowd_info' by focusing on PDF creation rather than information retrieval. However, it doesn't explicitly differentiate from other potential PDF creation tools beyond mentioning not to use other PDF tools on errors.

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 explicit guidance on when and how to use this tool: it instructs to call 'pdfcrowd_info' for parameters and layout guidelines before use, specifies not to pass PDFCrowd API parameters, and gives clear error-handling instructions ('Report configuration issues to the user instead of trying other PDF tools'). This covers when to use alternatives and prerequisites effectively.

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