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

readOnlyHint=true already establishes the safe-read profile, and the description adds genuinely non-obvious response semantics: refunds are returned as negative amounts. That is a behavioral detail no annotation or schema conveys. It stops short of mentioning pagination behavior even though two pagination parameters exist.

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?

Two short sentences, zero filler: the operation and its one non-obvious return convention come first, followed by the endpoint reference. Nothing is padded.

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?

For a simple read tool with a fully documented schema, the description covers what is returned (payments plus negative refunds) and the target scope. No output schema exists, yet the response shape is described at an adequate level; the only omitted behavior is pagination workflow, which the schema already explains.

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 100%, so all four parameters are self-documenting (including the pagination token mechanics). The description only confirms that bookingNumber selects the target booking and adds nothing about pageNumber/itemsPerPage. Baseline 3 applies.

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?

States a specific verb ('List') and resource ('payments ... received for one booking'), with the scoping phrase 'for one booking' that separates it functionally from the sibling bookeo_list_payments (all payments). It does not name that sibling explicitly, so the differentiation is inferable rather than stated.

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 phrase 'for one booking' implies the use case (you already have a bookingNumber and want its payment history), but there is no explicit guidance on when to prefer this over bookeo_list_payments or bookeo_get_payment, nor any stated prerequisites.

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