get_invoice_payments

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

The description mentions pagination, which is a behavioral trait. However, with no annotations, there is no disclosure of read-only status, required permissions, side effects, or other behavioral details. The pagination note provides 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 concise sentence that front-loads the purpose and key feature (paginated). No extraneous information, 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 lacks details on return format, pagination mechanics, error handling, or any additional context. For a list tool with multiple parameters, this is insufficient for complete understanding.

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%, and the description adds no information about the parameters (invoice_id, workspace_id, page, page_size). The schema titles provide some meaning, but the description fails to clarify their semantics or usage, scoring below adequate.

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 tool lists an invoice's payments with pagination. It uses specific verbs and resources ('List an invoice's payments'), and the parenthetical '(paginated)' adds important detail. It is easily distinguishable from sibling tools like get_invoice or list_invoices.

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. There is no mention of context, prerequisites, or exclusions, leaving the agent without direction on appropriate usage.

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