list_cash_payments

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior but does not explicitly state that it is read-only or require special permissions. For a straightforward list tool, this is adequate but could be improved by mentioning that no data is modified.

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 extremely concise with two sentences. It front-loads the purpose and immediately follows with key features (pagination and filters). Every word adds value.

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 covers the core purpose, pagination, and filter options. However, no output schema exists, and the description does not explain the return fields or how to navigate pagination beyond basic parameters. For a list tool with 7 parameters, slightly more detail on response structure would improve completeness.

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%, with each parameter already described. The description adds a summary of filter options but does not provide additional meaning beyond what the schema offers. Baseline 3 applies because the schema covers the parameters well.

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 explicitly states 'List payments made to suppliers', which is a specific verb+resource. The name and description clearly distinguish from siblings like record_cash_payment (create) and list_cash_receipts (customer receipts).

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?

Description mentions pagination and three filter options, providing useful context for when to use the tool. However, it does not explicitly state when not to use it or compare with alternatives like list_bills or list_cash_receipts, leaving some guidance implicit.

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