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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds useful behavioral context beyond annotations: default page size 25, maximum 200, next-page logic (offset + limit), and the POST endpoint for a read operation. It does not describe rate limits or authentication, but those are secondary for a read-only list.

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 four sentences, front-loaded with the core purpose and capabilities, then paging and field naming. Every sentence adds value, and there is no redundant fluff.

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 no output schema, the description covers paging behavior, default/max limits, field naming conventions, and the endpoint. It does not explain the response shape, but given the absence of an output schema, this is a minor 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%, so the baseline is 3. The description adds concrete field-name examples (receiptId, receiptType, issuedDate, dueDate) that are not present in the schema and help agents construct filters, field selections, and ordering. The paging formula is also restated helpfully.

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 clearly states the verb 'List' and resource 'customer payments received (cobros)', and it enumerates capabilities (filters, sorting, field selection, paging). It does not explicitly distinguish this tool from close siblings like laudus_sales_invoice_receipts, so it falls 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?

Usage is implied by the resource name and the paging instructions, but there is no explicit guidance on when to use this tool versus alternatives such as laudus_list_sales_invoices or laudus_sales_invoice_receipts. No exclusions or prerequisites are stated.

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