list_bill_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 of behavioral disclosure. It indicates the tool is a read operation ('list') but does not disclose potential behaviors such as pagination, ordering, filtering by status, or the possibility of an empty list. Without annotations, the description is too sparse to set expectations for the agent.

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, efficient sentence with no fluff or redundancy. It is front-loaded with the main action. While it is very brief, it effectively communicates the core purpose without wasted words, which fits the concise nature of a simple list tool.

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 the tool's low complexity and the existence of an output schema (which likely documents return values), the description is minimally adequate. However, it lacks context about what the list includes (e.g., all payments, statuses), and it relies heavily on the tool name and sibling context. For a simple list operation, this is sufficient but not comprehensive.

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. It indirectly implies that bill_id is the identifier of the bill for which payments are listed, but it does not explain the meaning of the parameter, any constraints, or format. The description adds minimal value beyond the schema's parameter name.

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), the resource (payments), and the scope (for a specific bill). This distinguishes it from siblings like get_bill_payment (single payment) and create_bill_payment (creation), and from list_bills (which lists bills, not payments). The wording is specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that get_bill_payment should be used for a single payment, or that create_bill_payment should be used for adding payments. There is no mention of prerequisites or exclusions. The only contextual hint is that it requires a specific bill, but this is implicit rather than explicit.

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