factures

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

With no annotations, the description carries full behavioral burden, yet it only restates purpose. It doesn't mention pagination behavior, the 'limit' default, or the shape of returned data, all of which matter for a list endpoint.

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 front-loaded sentence with the core purpose first and filters second; every clause adds information. It is efficient, though a bit terse given the coverage gaps.

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?

No output schema or annotations exist, so the description should do more. It covers purpose and two filters but omits pagination/'limit' semantics and return structure, leaving gaps for an agent invoking it.

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 0%, so the description must compensate, and it does partially: it clarifies 'chantier_id' means the site number within the account and that 'statut' filters by status. The 'limit' parameter and valid 'statut' values remain undocumented.

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 ('Liste les factures émises'), and adds scope via the optional filter mention. It's clearly distinguishable from the singular sibling 'facture', but it doesn't explicitly name alternatives like 'factures_impayees'.

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?

The phrase 'éventuellement filtrées par statut ou chantier' implies how the filters are used, giving modest usage context. It never states when to prefer this tool over siblings such as 'facture' or 'factures_impayees', and offers no exclusions.

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