get_invoice_reminder_pdf

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety expectations. However, the description adds no behavioral context beyond the tool name—it does not disclose what 'show' entails (e.g., generating a file, returning a URL, downloading), any authentication requirements, or response format. This is essentially a tautology of the name.

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 extremely short at only three words, which is concise but under-specified. It is front-loaded but has no informational substance beyond what the tool name conveys. Adequate in length but not appropriately sized for the tool's complexity.

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 should at least hint at the return value (presumably a PDF file), but it does not. It also fails to mention the required combination of invoice_id and reminder_id or any behavior like letterhead generation. The annotations cover safety but not functional completeness. For a 3-parameter tool with no output schema, this is insufficient.

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?

Input schema has 100% description coverage, with invoice_id and reminder_id clearly defined as IDs and logopaper explaining the letterhead option. The description adds no parameter information, but since the schema is comprehensive, the baseline of 3 is appropriate.

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 'Show reminder PDF' clearly indicates the tool retrieves or displays a reminder PDF. The verb 'show' and resource 'reminder PDF' are specific enough, but it does not explicitly distinguish from other PDF-related tools like get_invoice_pdf or get_order_pdf beyond the 'reminder' qualifier, relying on the tool name for full context.

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?

No guidance is provided regarding when to use this tool versus alternatives. Sibling tools such as get_invoice_reminder (non-PDF) and get_invoice_pdf exist, but the description does not mention them or clarify that this is the PDF-specific variant for reminders. No prerequisites or exclusions are stated.

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