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

Annotations already declare readOnly/openWorld/non-destructive, so safety is covered. The description adds behavior the annotations do not: default page size of 25, a hard cap of 200 rows, the offset-advance pattern, and the underlying endpoint POST /sales/invoices/list — all useful for planning calls.

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, front-loaded with the scope and pagination rule, then the field-naming detail. The field enumeration is long but earns its space because field names are otherwise unknown; nothing is redundant 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?

For a read-only list tool with a fully documented schema and no output schema, the description covers scope, paging semantics, and field vocabulary. The only remaining gap is that it does not characterize the shape of returned rows, though the field examples implicitly do so.

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%, so the baseline is 3, but the description goes further by enumerating concrete Laudus field names (salesInvoiceId, docType.name, customer.VATId, totals.net, items.product.sku) that an agent would otherwise have to guess. That is genuine added meaning beyond the schema's generic nested-name hint.

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 and resource and scopes it to include electronic tax documents ('facturas, notas de credito'), which is meaningful in a Latin American ERP context. It does not explicitly contrast itself with the single-record sibling laudus_get_sales_invoice, but the 'List' verb and plural resource make the distinction legible.

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 gives concrete operational guidance for pagination ('When a page is full, ask for the next one with offset = offset + limit'), which is real usage help. However it never states when to reach for this tool rather than laudus_get_sales_invoice or laudus_sales_invoice_receipts, so selection guidance is left implicit.

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