merit_create_purchase_invoice_payment

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

With no annotations, the description carries the burden and does disclose a mutation ('Record a payment'), the endpoint, and the paymentDate format conversion. However, it omits any detail about response behavior, permissions, or whether the payment can be reversed.

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 tightly written sentences. The purpose is front-loaded, followed by the identification rule and the key format transformation, with no redundant wording.

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?

The description is enough to invoke the tool with required parameters and understand the date conversion, but it lacks guidance for optional parameters and doesn't specify expected behavior/response. Given no output schema or annotations, this is a moderate gap rather than a fatal one.

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 description adds meaning beyond the schema by explaining that vendorName and billNo identify the target bill and that paymentDate is converted to yyyyMMddHHmm. But the four optional parameters (iban, refNo, bankId, currencyCode) remain unexplained, and schema coverage is only 50%.

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 the action 'Record a payment' and the exact resource 'purchase invoice', with the API endpoint in parentheses. This clearly separates it from the sales invoice and sales offer payment siblings.

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 gives clear context for when to use it: recording a payment against a purchase invoice, identified by vendorName and billNo. It does not explicitly name alternative tools or when-not conditions, but the purchase-invoice framing is sufficient.

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