apply_incoming_payment

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

Since no annotations are provided, the description carries the behavioral burden. It discloses a meaningful non-obvious behavior: the amount is distributed proportionally across open invoice balances. However, it does not describe side effects such as whether the payment is fully posted, how overpayments or underpayments are handled, or whether the operation is reversible.

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 two sentences with no filler. The primary action and the proportional-distribution behavior are front-loaded, so an agent can immediately understand the tool's core function without parsing unnecessary detail.

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?

For a financial mutation tool with no annotations, no output schema, and eight parameters, this description is too incomplete. It lacks prerequisites, guidance on which accounts to use, and the post-application financial effects, so an agent would need to guess at significant business context before invoking it correctly.

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 only 13%, with only 'docDate' described, and the description barely compensates for the other parameters. It connects 'amount' to the payment and 'invoiceDocEntries' to invoices, but it leaves 'cardCode', 'cashAccount', 'transferAccount', and 'transferReference' unexplained, making it hard for an agent to populate most parameters confidently.

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, 'Apply', with a clear resource: an incoming payment against one or more invoices, and it adds the business goal of reconciling A/R. This clearly differentiates it from the sibling 'apply_outgoing_payment' by payment direction.

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 implies this is for incoming payments and A/R reconciliation, but it never explicitly says when to use this tool versus alternatives like 'apply_outgoing_payment' or 'create_ar_invoice'. The usage context is inferable but not directly stated, and there are no exclusion criteria or prerequisites.

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