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 only the underlying GET endpoints, which confirms read semantics but says nothing about pagination, result size, or whether partially paid invoices count as pending.

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?

Three short, front-loaded sentences with the purpose first and the scoping rule second. The endpoint URLs are the weakest element – useful for orientation but partially redundant filler for an agent that invokes by tool name.

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 one-parameter read tool with annotations this is nearly sufficient, but with no output schema the description should at least sketch what a pending invoice record contains (amount, due date, currency) or how 'pending' is defined. That gap leaves an agent guessing about the return payload.

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% and the single parameter's own description already says 'omit for every customer'. The description repeats that same fact plus the positive constraint, so it adds no semantics beyond the schema; baseline 3 applies.

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 resource and qualifier: 'Unpaid sales invoices (accounts receivable)'. That distinguishes it well from the sibling laudus_list_sales_invoices, but the differentiation is implied by the word 'Unpaid' rather than called out explicitly.

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?

Explains the customer_id scoping choice ('Give customer_id for one customer, or leave it out for all customers'), which is usage of the parameter rather than guidance on when to pick this tool over laudus_list_sales_invoices or laudus_balance_sheet. No exclusions or alternatives are named, so usage is only implied.

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