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

Annotations only flag it as a non-idempotent write; the description adds material context they don't carry: credit consumption per template rendered, that identical-data retries still bill, hosted URL expiry tied to `expiration` minutes, and latest-version resolution. No contradiction with destructiveHint=true since the billable write profile is disclosed.

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?

Front-loaded with a 'WRITE:' signal and the credit warning, then the operation, then the return value and endpoint. No filler sentences, but the parenthetical cost clause is dense enough that it competes with the core purpose statement for attention.

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?

With no output schema, the description still explains the return (expiring hosted URL), the cost model, count limits, and the underlying endpoint. Minor gaps remain — no mention of failure/retry behavior or what happens if a template id is invalid.

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 the baseline is 3. The description adds the cost consequence of the `templates` array size, the data fallback relationship, and expiry semantics behind `expiration` — meaningfully more than restating the fields, though `paging` and `output_file` get nothing.

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?

States a specific verb and resource with exact scope: 'Generate ONE combined PDF from 2-10 templates, each with its own data (or the shared `data`)'. This clearly distinguishes it from sibling craftmypdf_create_pdf (single template) and craftmypdf_merge_pdfs (existing PDFs) without needing the schemas.

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?

Gives clear conditions for use — 2-10 templates, per-template data with shared fallback, latest template versions — and connects cost to template count. It never explicitly names the alternatives (create_pdf, merge_pdfs) or states when NOT to use it, so routing still requires inference from sibling names.

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