list_purchase_payments

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

The description reveals only the default sort order. Without annotations, it fails to disclose that the tool is read-only, requires authentication, or any potential side effects. For a list operation, this is minimal transparency.

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 a single, front-loaded sentence with no wasted words. It efficiently states the core function and default behavior.

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?

Despite the presence of an output schema and six input parameters, the description does not cover important contextual aspects like when to use the tool, what a 'purchase payment' represents, or how the output relates to other tools. It is insufficient for an agent to fully understand the tool's role.

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. The description adds no extra insight beyond the schema's parameter descriptions, such as the default sort being '-date' which is already stated. No additional semantic value.

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 clearly states the action ('List purchase payments') and the default ordering ('newest first'), which distinguishes it from other list tools like list_sales_documents. However, it does not specify that it returns multiple records as opposed to a single payment via get_purchase_payment.

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 on when to use this tool versus alternatives such as get_purchase_payment for a single payment or create_purchase_payment for creating payments. The description lacks any contextual advice.

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