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 valuable behavior beyond that by enumerating the return fields (id, invoice_number, totals, balance_due, due_date, status, customer name), which matters because there is no output schema. It does not mention pagination or default row counts.

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?

Compact and front-loaded: the verb+resource comes first, then the filter definitions, then the return fields. It is dense but every clause carries information, though the parenthetical predicate list is slightly run-on for a single sentence.

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 safety profile and no output schema, the description fills the important gaps: filter predicates and return-field shape. The only unwritten piece is limit/pagination behavior, which the schema already documents, so the definition is nearly complete for this tool's complexity.

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%, which sets a baseline of 3, but the description goes further by defining the exact predicate behind each enum value (e.g. overdue = due_date<today AND balance_due>0 AND not paid/cancelled/refunded), replacing the schema's vague 'Invoice state filter.' That is meaningful added semantics the schema does not carry.

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 ('Find invoices') and immediately defines the three filter modes with exact predicates, so the agent knows precisely what the tool retrieves. It does not, however, distinguish itself from near-neighbors like get_ar_aging or ar_aging, which likely also surface receivables.

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 only implied by the tool name and filter semantics; there is no explicit statement of when to prefer this over ar_aging, get_ar_aging, or quotes_to_follow_up. The detailed filter conditions help the agent pick a mode once it has decided to call the tool, but they do not guide tool selection.

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