list_payments

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'List', implying a read-only operation, but does not explicitly confirm non-mutating behavior, permissions, or any side effects. No additional behavioral context is provided.

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 front-loads the core purpose and includes the optional filter. It is concise and avoids redundancy, making it easy to parse quickly.

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 minimal and does not clarify what constitutes a 'payment' or any nuances of the data returned. Since an output schema exists, return format is not required, but the lack of context about payment semantics or pagination (relevant to max_items) leaves the tool incomplete for an agent unfamiliar with the domain.

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 clarifies the booking_id parameter as an optional filter ('optionally for a single booking'), but does not explain max_items at all. With zero schema-level parameter descriptions, this partial clarification adds some value but leaves one parameter completely unaddressed.

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') and the resource ('guest payments'), and specifies an optional filter by booking. This is a specific, concise statement that distinguishes it from other list_* siblings like list_bookings or list_properties.

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 usage via the optional booking filter, but it does not explicitly mention when to use this tool instead of alternatives (e.g., when to use list_payments vs list_refunds). No conditions or exclusions are provided beyond the optional booking parameter, leaving some ambiguity.

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