pdf_create

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

Adds valuable behavioral details beyond annotations: automatic line wrapping, page overflow handling, and supported page sizes (A4/Letter/Legal). However, it omits file overwrite behavior despite idempotentHint: true suggesting idempotent writes.

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?

Two efficient sentences with zero waste. First sentence delivers core functionality and key behaviors; second sentence specifies format constraints. Information is front-loaded and dense.

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?

Appropriately complete for a creation tool with well-documented schema and safety annotations. Covers main functionality and key text-rendering behaviors. Lacks output description, but no output schema exists to require such coverage per guidelines.

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 has 100% coverage (baseline 3). Description adds semantic value by explaining how 'content' is processed (line wrapping/overflow) and explicitly listing valid page sizes that match the pageSize enum, enhancing understanding of parameter behavior.

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?

Description clearly states the specific action ('Create a new PDF'), the input source ('from text content'), and distinguishes from siblings like pdf_create_from_markdown and pdf_create_from_template by emphasizing plain text processing.

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?

Implies usage by specifying 'text content' as input, differentiating it from markdown/template variants, but lacks explicit guidance on when to choose this over pdf_create_from_markdown or file system constraints.

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