list_invoices

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

With no annotations and no description behavioral traits (e.g., pagination, ordering, filtering, side effects), the description fails to disclose any behavioral information. The agent receives no insight into what the tool does beyond listing invoices.

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?

While brief, the description is under-specified and does not earn its place by providing valuable information. It constitutes a tautology rather than conciseness.

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?

Given the tool's simplicity (no parameters, no output schema, no annotations), a minimal description might suffice, but this description provides no contextual completeness: it doesn't state what invoices are, return format, or any filtering capabilities.

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 input schema has zero parameters and is fully covered (100% coverage), so the baseline is 3. The description adds no further meaning beyond the schema, but this is acceptable for a parameterless tool.

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 'Lister les factures' is a French translation of the tool name 'list_invoices', effectively restating the name without adding any additional specificity or differentiation from sibling tools like list_clients or list_products.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent without direction for selection.

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