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

Annotations already declare readOnlyHint=true and the description reinforces 'Lecture seule', but it adds real value beyond them by describing what the result contains: one periodicity plus legal obligations per equipment (chaudiere annuelle, PAC tous les 2 ans) and that declared manufacturers are attached to the equipment. No output schema exists, so this content disclosure matters; it stops short of detailing volume, pagination or error cases.

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 condition is front-loaded and the parenthetical equipment list and examples earn their space by making the scope concrete. The trailing 'Lecture seule' is redundant with annotations but costs only three words.

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 one-parameter, non-destructive read with no output schema, the description covers the trigger, the scope (all equipment in the scene), and the content of the produced logbook. An agent has everything needed to decide to call it and to interpret the result.

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 100% for the single 'scene' object, so the schema already documents the parameter. The description only implies that the scene is a CAO model containing equipment, adding no format or preparation guidance beyond the schema baseline.

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 artifact ('produire le carnet d'entretien (exploitation) d'une scene') and enumerates the equipment types covered, so the agent knows exactly what it yields. It does not explicitly differentiate itself from the many sibling cao_bim_* tools, but the resource noun is distinctive enough to disambiguate.

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?

'Appelez quand vous devez produire le carnet d'entretien' gives a concrete trigger condition with a clear context (exploitation of a scene). No exclusions or named alternatives are given, so the agent must infer that e.g. cao_bim_cvc or cao_bim_fabricants serve other purposes.

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