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

Annotations declare non-read-only, non-destructive, open-world, but the description goes well beyond them: a draft does not post to the GL, overpayment remains an unallocated advance, each call is confirmed by default, and the action reaches other people requiring user confirmation. It also discloses the API key requirement, covering auth context.

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?

Front-loaded with what the tool does before behavioral caveats, and every clause carries information. The two adjacent confirmation sentences ('you confirm each call' and 'confirm with the user before each call') are slightly redundant, costing a little tightness.

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 draft-create mutation with no output schema, it covers document state (draft, not posted), allocation and overpayment behavior, the submit path, confirmation requirements, and auth needs. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: 'party' is the customer, invoices are allocated under References in oldest-due-first order, and payment amounts exceeding the invoices leave an unallocated advance. This clarifies behavior of paid_amount and invoices beyond the field descriptions.

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 specific verb and resource ('Saves a draft Receive payment entry'), specifies the resulting document type and its allocation scope, and explicitly distinguishes itself from the erpnext_submit_payment_entry sibling. An agent can tell this apart from submit_payment_entry without opening either schema.

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?

Names the alternative ('call submit_payment_entry') and the condition that selects it (posting to the General Ledger). It also states the confirmation default and how to change it, giving explicit operational guidance rather than leaving it to inference.

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