pdf_invoice

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It meaningfully reveals that output is deterministic and byte-identical (safe to re-run) and that unpaid usage adds a footer line. These are valuable, non-obvious behaviors beyond simply 'generate a PDF'.

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 tight, front-loaded with the core purpose, and every sentence adds value: the no-template qualifier, the deterministic guarantee, and the key-dependent footer caveat. No filler or redundant restatement of the schema.

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 that the schema fully documents the two parameters and the description covers determinism and licensing side effects, this is quite complete for selecting and invoking the tool. It could add a note about overwrite behavior or return value, but the core invocation context is well covered.

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 invoice and output_path parameters are already documented structurally. The description adds no additional parameter-level meaning beyond the schema, matching the baseline for high schema coverage.

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 uses a specific verb ('Generate'), a clear resource ('invoice PDF'), and a defining characteristic ('from structured data — no template needed'). This cleanly distinguishes pdf_invoice from siblings like pdf_fill and pdf_merge, which serve different purposes.

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 clearly implies when to use this tool: when an invoice PDF needs to be generated from structured data. However, it does not explicitly mention alternatives or when-not-to-use conditions, leaving the routing decision mostly to inference rather than direct guidance.

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