pdf_create_from_template

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

Adds valuable context about template-specific data requirements and document types beyond annotations. Aligns with annotations (readOnly=false supports 'Create'). No contradictions.

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 sentences with zero waste: first establishes purpose with examples, second provides critical usage instruction. Front-loaded and efficient.

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?

Sufficient for a creation tool with comprehensive schema documentation and safety annotations (idempotent, non-destructive). Absence of output schema noted but file path parameter clarifies output destination.

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?

With 100% schema coverage, the description adds semantic meaning by emphasizing that data must match template expectations, reinforcing the schema's detailed field requirements without redundancy.

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?

Clear specific verb 'Create' with resource 'PDF' and explicit template types (invoice, report, letter) that distinguish it from generic pdf_create and markdown-based siblings.

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?

Provides implied guidance via 'Pass structured data matching the template's expected fields' but lacks explicit when-to-use guidance comparing it to pdf_create or pdf_create_from_markdown alternatives.

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