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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the definition of 'overdue' (past due date) and no ordering, pagination, date-range, or inclusion rules, so it contributes modest extra context.

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?

A single short sentence that front-loads the resource and its filter with no filler. It is efficient, though it is arguably under-specified rather than genuinely concise.

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 annotations covering the read-only safety profile and an empty input schema, the core mechanics are adequately conveyed. The missing piece is routing: nothing tells the agent how this differs from list_unpaid_invoices or list_recent_invoices.

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?

The tool takes zero parameters, so per the baseline the schema needs no compensating explanation. The phrase 'the business you picked' references ambient context rather than any documented input, which is mildly ambiguous but not a true parameter gap.

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 (invoices) and a scope qualifier (past their due date), so the filter is clear. However, it never differentiates itself from the sibling list_unpaid_invoices, which an agent could easily confuse with 'overdue' since the two filters overlap but are not identical.

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?

There is no when-to-use guidance, no mention of alternatives (list_unpaid_invoices, list_recent_invoices), and no stated conditions for choosing this tool. The trailing phrase 'for the business you picked' hints at an implicit selected-business context but does not explain how or when that context is set.

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