generate_invoice_pdf

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

With no annotations, the description must bear full burden. It discloses that save_path triggers file output, and that a hosted link expires in 7 days. However, it doesn't specify the impact of missing API key, confirmation of non-destructiveness, or any rate limits, leaving gaps.

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 sentences, each adding essential information: purpose, mode selection, and configuration. No redundant or filler content; highly 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?

Given the tool's high complexity (21 parameters, nested objects, no output schema), the description is too brief. It lacks details on API key consequences, hosted link format, failure modes, and overall behavior, leaving an agent under-informed for correct invocation.

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?

The input schema covers 62% of parameters with descriptions, but the tool description adds little beyond mentioning save_path. It does not explain the return behavior beyond the two modes, and does not clarify the meaning or interaction of many parameters (e.g., templates, color, payment info).

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 'Generate a PDF invoice', specifying both the verb and resource. It distinguishes from sibling tools by focusing on PDF output and mentions two modes of return (hosted link vs file), making its purpose specific and unambiguous.

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?

Explicitly describes two distinct usage paths: default for chat (hosted link) and local file via save_path. Mentions the need for an API key for reliable output. While it doesn't directly compare to siblings, the differences are clear enough.

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