pdf_create

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

Adds behavioral details beyond annotations: automatic line wrapping, page overflow handling, and fontPath for non-Latin support. Annotations already indicate it's a write (readOnlyHint=false) and idempotent (idempotentHint=true), so the description complements well without contradiction.

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 succinct, front-loaded sentences covering core function, page size support, and fontPath guidance. Every sentence adds value with no wasted words.

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?

Covers the main behavior and constraints. With full schema coverage and annotations, the description is sufficient for a tool of this complexity. Could mention whether outputPath overwrites existing files, but idempotentHint implies safety.

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 100% so each parameter is described. The description reinforces the fontPath parameter's purpose for non-Latin text but adds little new meaning 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?

Explicitly states 'Create a new PDF from text content' with automatic line wrapping and page overflow. Mentions supported page sizes and fontPath for non-Latin. Differentiates from siblings like pdf_create_from_markdown and pdf_create_from_template by focusing on plain text input.

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 for plain text via 'from text content', and hints at alternatives through sibling tool names, but does not explicitly state when to use this vs others or mention any exclusions.

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