list_payments

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits like pagination behavior (implied by parameters but not described), authentication needs, rate limits, or what 'list' returns. It's minimal and lacks operational 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?

The description is extremely concise with a single sentence, 'List all payments,' which is front-loaded and wastes no words. It's appropriately sized for a simple tool, though this brevity contributes to gaps in other dimensions.

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?

Given low complexity, 2 parameters with 0% schema coverage, no annotations, but an output schema exists, the description is incomplete. It doesn't explain the pagination behavior hinted by parameters or what the output contains, though the output schema may cover return values. It's minimally adequate but with clear gaps.

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 0%, so the description must compensate, but it adds no meaning beyond the schema. Parameters 'page' and 'per_page' are undocumented in the description, though their presence implies pagination. Baseline is 3 as the schema provides structure, but the description fails to explain parameter roles.

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 'List all payments' states a clear verb ('List') and resource ('payments'), but it's vague about scope and doesn't differentiate from sibling tools like 'get_invoice' or other list tools. It lacks specificity about what 'all' means in context.

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 like 'get_invoice' for specific payment details or 'list_invoices' for related resources. The description offers no context about prerequisites or exclusions.

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