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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, and the description reinforces this with 'Lecture seule'. It also adds useful behavioral context beyond the annotations: the signature remains human and the result includes a consolidated verdict with failing pieces, average score, and readiness to sign.

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 purpose is front-loaded in the opening clause, and the long enumeration of included BIM pieces is directly relevant to helping an agent understand scope. It is dense and could be formatted more readably, but there is little wasted material.

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 complex 13-parameter aggregator with no output schema, the description covers the essential output concept: a consolidated verdict with failing pieces, average score, and readiness to sign. Parameter details are mostly left to the high-coverage schema, and error behavior or exact return structure is not specified, which keeps it from a 5.

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 92%, so the input schema already documents almost all parameters. The description adds a useful pointer that parameters match cao_bim_projet action=dossier plus seuils and date_limite, but it does not explain individual parameter meaning or constraints beyond what the schema provides.

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 aggregate action: producing the complete DCE package in one call, and enumerates both the historical dossier contents and all added BIM pieces. This clearly distinguishes it from the many sibling tools that produce individual pieces such as cao_bim_cctp, cao_bim_acv, or cao_bim_incendie.

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 gives an explicit usage condition: call it when you want the complete DCE dossier in one call, and it points to cao_bim_projet action=dossier for matching parameters. It does not explicitly say when not to use it or name individual piece tools as alternatives, so it falls short of full when/when-not guidance.

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