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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds nothing further. It does not mention pagination behavior, ordering of the returned payments, or whether an empty list vs. an error results from an invoice with no payments. For a list tool this is thin, but not contradictory.

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?

It is certainly short, but it is a sentence fragment rather than a front-loaded structured statement, so the minimal length reflects under-specification more than disciplined editing. Nothing is redundant, yet nothing is organized for quick scanning either.

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?

This is a simple read tool with full schema coverage and a readOnly annotation, so the bar is modest, but the description still leaves the agent unsure whether payments also appear inside bokio_get_invoice and how results are ordered or paged. A single clause distinguishing it from that sibling would have closed the gap.

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 coverage is 100% — invoiceId is documented as a GUID pattern and page/pageSize have ranges and defaults — so the schema carries the parameter burden. The description adds only the implicit constraint that invoiceId must refer to a single sales invoice, which is marginal but slightly useful.

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 fragment identifies the resource — payments tied to a single sales invoice — which is more specific than the name alone. But it is a noun phrase with no verb, so the fact that this is a paginated list operation comes only from the tool name, not the description. An agent can guess what it returns but not how it behaves.

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?

There is no statement of when to use this versus alternatives such as bokio_get_invoice (which may or may not embed payments) or bokio_list_invoices. Nothing excludes it from related scenarios, and no prerequisites (e.g., the invoice needing to exist, or being a sales invoice rather than a supplier invoice) are mentioned.

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