payments_receipt_pdf

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description contributes what the document actually contains (company, payer, amount in figures and words, settled invoice, payment date) and its A5 landscape format, which is genuinely useful, but says nothing about delivery form (binary stream vs. link), permissions, or the error case of a payment without an issued receipt.

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 compact sentences, front-loaded with the action and resource, with the document contents following as supporting detail. No filler or restated title; the only mild inefficiency is that the content list is optional context rather than operational guidance.

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?

There is no output schema, so the description usefully compensates by describing the generated document's layout and data fields, which is the main thing an agent would otherwise lack. The remaining gap is that it doesn't state the returned representation (PDF bytes/base64/file URL), which matters when no output schema exists.

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 all three parameters are already documented in the schema. The description reinforces that this applies only to cash payments (relevant to paymentId) and identifies invoiceId as the settled invoice, but adds no syntax, format, or defaulting guidance beyond the schema — baseline 3 applies.

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 concrete verb+resource ("Download the PDF of the chitanță issued for a cash payment") and scopes it to cash receipts, cross-referencing the issuing tool payments_receipt_issue. It stops short of distinguishing itself from the separate receipts_pdf / receipts_* family in the sibling list, which an agent could confuse with this one.

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 parenthetical "(see payments_receipt_issue)" implies the receipt must be issued before the PDF can be downloaded, and "for a cash payment" narrows the applicable case. However there is no explicit when-to-use statement, no rejection of alternatives (e.g. receipts_pdf, invoices_pdf), and no stated behavior when no receipt has been issued.

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