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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds the concrete endpoint (GET /v1/payments.json) and the returned field set, but says nothing about pagination behavior beyond what the schema states or about result volume.

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 tight sentences: the first covers output shape, the second covers filtering, and the endpoint closes it out. No filler and the returned-field list is front-loaded.

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?

With no output schema, the description usefully compensates by naming the fields returned, and it covers the main filter dimensions. Minor gap: it doesn't mention pagination or expand, though those are schema-documented, so an agent can still call it correctly.

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 71%, so most parameters are already documented, and the description reinforces the paid_on, document_id and code_sii+number pairing. It adds no syntax or format detail beyond the schema and omits limit/offset/expand entirely, so it is a baseline-level contribution.

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 opens with a specific verb and resource ('List payments received') and enumerates the returned fields (amount, date, payment type, document, office, user), so the agent knows exactly what this returns. It does not explicitly differentiate itself from siblings like bsale_list_payment_types or bsale_list_documents, keeping it just short of a 5.

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?

It states the available filters (payment date, document id, tax code plus folio), which implies how to narrow results, but there is no guidance on when to choose this over sibling listing tools or when filters are required. Usage is inferable but not spelled out.

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