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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context that results include summary stats on outstanding and overdue amounts, but it does not discuss pagination, result limits, or output structure.

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 sentences are tightly written, with the core purpose and key output detail front-loaded. Every sentence contributes to helping an agent decide whether to invoke the tool.

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 invoice listing tool with full parameter descriptions and safety annotations, the definition is largely complete. It still omits sibling differentiation from other invoice-related tools and says nothing about result volume or pagination, which are minor gaps rather than blockers.

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 description coverage is 100%, so the schema already documents search, status, company, and contact_id thoroughly. The description does not add parameter-specific meaning beyond what the schema provides, which is acceptable given the high coverage.

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 states a specific verb and resource: getting invoices raised by the user, plus summary stats on outstanding and overdue amounts. It is clear what the tool returns, but it does not distinguish this tool from siblings such as deel_get_invoices or get_recurring_invoices.

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?

It gives clear usage context: use when the user asks about invoices, outstanding payments, or money owed to them. It does not explain when to use alternatives like deel_get_invoices or get_recurring_invoices, so the guidance stops short of full sibling routing.

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