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

Annotations already declare readOnlyHint=true / destructiveHint=false, and the description simply restates that with 'Lecture seule'. It does add real context: the default output is markup XML ready for Solibri/BIMcollab and the reserves path produces a DTU snag list, but it says nothing about what the importer returns or how large/complex scenes are handled.

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 trigger ('Appelez quand...') is front-loaded and every clause carries information; no filler. The single sentence with two levels of nested parentheses is dense and slightly harder to parse than a short bulleted mode list would be.

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 three parameters with full schema coverage and annotations covering the safety profile, the definition is mostly sufficient. However, with no output schema, the return value for action=importer and action=reserves is left unspecified, and the nested scene object's expected structure is only alluded to.

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 100%, so baseline is 3, but the description goes beyond the schema by explaining what each action value produces and confirming zip_base64 is only for action=importer. The scene parameter itself gets no added semantic detail beyond the schema's format hint.

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: generate BCF 2.1 issues from IFC round-trip deviations, with the three operating modes (default scene, reserves/snag list, external ZIP import) spelled out. The scope is clear, but it never distinguishes itself from close siblings such as cao_bcf_ifc, cao_bim_aller_retour or cao_bim_reception, so an agent cannot route between them from this text alone.

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?

Explicitly opens with 'Appelez quand vous devez...' and gives a condition per mode: default when working from scene deviations, action=reserves when a reception snag list (DTU) must go to coordination, action=importer when reading an external BCF ZIP. Missing only when-not-to-use and explicit pointers to the overlapping sibling tools.

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