pdf_create

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool creates a PDF but doesn't mention side effects (e.g., file system writes), permissions needed, error conditions, or output format. For a tool that writes files, this lack of transparency about its behavior and potential impacts is a significant gap.

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 a single, clear sentence that efficiently conveys the core function without unnecessary words. It's front-loaded with the main action and resource, making it easy to parse. Every word earns its place, and there's no redundancy or fluff.

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 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success status, file path), error handling, or behavioral details like file overwriting. For a creation tool with moderate complexity, more context is needed to guide effective use.

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 description coverage is 100%, so the schema fully documents all parameters (output, text, title, fontSize). The description adds no parameter-specific information beyond implying 'text' is the content source. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description doesn't enhance understanding of parameter roles or 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 action ('Create') and resource ('PDF document from plain text content'), making the purpose immediately understandable. It distinguishes from siblings like pdf_merge or pdf_extract_text by focusing on creation from text rather than manipulation or extraction. However, it doesn't explicitly contrast with all siblings (e.g., pdf_set_metadata could also involve document creation aspects).

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing text content), when not to use it (e.g., for adding watermarks or merging existing PDFs), or refer to sibling tools like pdf_merge for combining documents. The agent must infer usage from the name and description alone.

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