Consulter l’historique BODACC

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

No annotations, so the description carries the full burden. It discloses the returned resource and that a family filter exists, but says nothing about ordering, pagination, the 50-item default/100 max, or whether history is bounded in time.

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 efficient sentence with the resource front-loaded. It wastes nothing, though its brevity is partly a symptom of under-specification rather than tight writing.

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 3-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description leaves out the required siren, the limit behaviour, and most enum values. An agent cannot invoke it confidently from this text alone.

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 only partially does. It alludes to the family enum via 'famille précise' and 'procédures collectives' (collective), but never mentions the required siren parameter, the limit default/maximum, or the other enum values (creation, modification, radiation, dpc).

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 (Retourne) and resource (annonces BODACC) with a scoping qualifier (récentes / d'une famille précise). It is understandable in isolation, but with no direct BODACC sibling named and no differentiation from the many other lookup tools, it stops short of a 5.

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?

There is no explicit when-to-use statement, no prerequisites, and no alternative tool named. The phrase 'ou celles d'une famille précise' hints at a filtering scenario but gives no guidance on when a caller should pick this over get_inpi_rne_record or search_judilibre.

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