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

Annotations already establish that this is a read-only, non-destructive, open-world operation, so the description correctly focuses on added context. It discloses the endpoint, the returned invoice fields, and the open-balance calculation, which meaningfully exceeds the annotations without contradicting them.

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 front-loaded and compact: the first sentence defines the operation and returned data, and the second adds a specific calculation note. There is no filler.

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?

Because there is no output schema, the description appropriately lists the invoice fields and explains open balance. It still omits the response envelope and pagination details such as next_skip, which would help complete the picture for a list endpoint.

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 the schema already carries the parameter documentation burden. The description adds a useful filter strategy for open balances, but it does not add meaning beyond the schema for top, skip, or orderby.

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 states a specific verb and resource ('List sales invoices') and enumerates the returned fields. It is clearly a list operation rather than a single-invoice get, though it does not explicitly distinguish itself from siblings like binderp_get_invoice or binderp_list_invoice_payments.

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?

Usage is mostly implied by 'List sales invoices'; there is no explicit guidance on when to use this instead of binderp_get_invoice or binderp_list_invoice_payments. The open-balance filtering hint is useful operational guidance but is not tool-selection guidance.

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