sezzle_list_settlement_summaries

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety and idempotency. The description adds that amounts are 'lossless minor-unit' numbers and that only 'documented' summaries are listed, providing some extra context. However, it does not disclose pagination behavior, ordering, or the meaning of 'documented'.

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, focused sentence that begins with the verb 'List' and omits unnecessary words. It conveys the essential purpose directly and efficiently.

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 too minimal to be fully complete given no output schema and four parameters. It does not mention the required date range, optional currency/offset, or what a 'summary' contains—information an agent would need to correctly invoke the tool. While annotations provide safety context, the description lacks operational 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?

The description offers no information about the tool's parameters. With schema description coverage at 0%, it does not compensate by explaining that start_date and end_date define the range, currency selects the denomination, or offset controls pagination. This is a significant gap for effective invocation.

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 a specific action ('List') and resource ('settlement payout summaries'), adding precision with 'lossless minor-unit amounts'. This distinguishes it from sibling tools like sezzle_get_settlement_details, which likely retrieve individual details rather than summaries.

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 tool is for listing summary records, but it does not explicitly state when to use it versus alternatives such as sezzle_get_settlement_details. No when-not conditions or alternative tool names are given, leaving the usage context somewhat inferred.

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