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

Annotations already mark this as a non-read-only, non-destructive, closed-world mutation. The description genuinely adds context beyond them: cancel preserves existing results, queue requires a connected agent, and the 'relire la version' note signals optimistic-concurrency behavior. It still says nothing about failure modes (e.g., version mismatch) or what the call returns after a state change.

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?

Very compact and front-loaded: the action semantics come first, the version caution last, with no filler. The terseness borders on cryptic ('confie une collecte'), and switching languages mid-tool reduces scannability, but nothing is wasted.

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 mutation tool with no output schema and zero schema documentation, the description covers the core actions, a prerequisite, and a concurrency warning. It is still missing what happens on version conflict, what 'results preserved' means operationally, and what the caller receives, so it is adequate rather than complete.

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 0%, so the description must carry the burden. It does explain the meaning of both 'action' values and gives the 'version' parameter concurrency semantics ('relire la version avant appel'), but 'id' is never described and the semantics of a version mismatch remain unstated.

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 names both operations concretely: 'queue' assigns a collection to MonAssocié and 'cancel' revokes that assignment. It never plainly restates that the tool mutates a collection's state, and it is written in French while the name/title are English, which slows matching slightly, but an agent can still tell what the tool does from the action semantics.

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 effectively explains the choice between the two enum values (queue vs cancel) and adds a prerequisite ('agent connecté requis'), which is real usage guidance. However, it gives no guidance relative to the many relevant siblings (claim_collection, delegate_task_to_monassocie, report_collection, update_collection, delete_collection) and no explicit when-not to call.

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