Factures d'une société

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so there is no contradiction. However, the description adds no behavioral context beyond the purpose, such as filters, pagination, sorting, or scope of invoices included. It only mentions the return type.

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?

The description is highly concise with a clear structure: a one-line purpose, an Args block, and a Returns line. Every part is necessary and there is no redundant information.

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 simple one-parameter read operation with robust annotations, the description is minimally acceptable. It states purpose and return type, but lacks usage guidance and clarification of invoice scope. Given many related invoice tools, the absence of alternative pointers leaves a gap.

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 100% description coverage for the id parameter ('Identifiant unique de l'entité BoondManager'). The description adds 'ID de la société', which clarifies the role but not any new semantic meaning beyond the schema. Baseline 3 applies.

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: 'Récupère les factures d'une société' (retrieves invoices of a company). It is clearly distinguished from global invoice search/get tools, though it doesn't explicitly differentiate from provider invoices (boond_companies_provider_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?

No usage guidelines are provided. The description does not indicate when to use this tool versus boond_invoices_search, boond_invoices_get, or boond_contacts_invoices, nor any exclusions or prerequisites.

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