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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent ("Lecture seule"). It adds real behavioral context beyond annotations: the 5D cost split by lot weights, day-by-day cumulative output in ISO dates, and the cash-flow derivation (30% deposit, monthly billing, 5% retention). It does not mention limits or caveats beyond "Indicatif".

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 every clause carries information, but the whole description is one overloaded colon-and-parenthesis sentence mixing purpose, computation weights, output format, mode selection and prerequisites. Abbreviations (ES/EF, CPM, 5D) go unexplained, which slows parsing.

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?

No output schema exists, but the description compensates by describing the returned data (day-by-day cumulative curve in ISO dates, monthly treasury), and the nested scene object is documented in the schema. Adequate for a read-only computation tool, though it never clarifies how the scene geometry feeds the CPM beyond "taches_personnalisees optionnelles".

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 the baseline is 3. The description still adds value by stating that "debut" is required even though the schema lists no required parameters, and by explaining how "action" switches between the curve and treasury outputs, which the schema only lists as enum strings.

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: produces the S-curve dated by the critical path (4D schedule) plus the monthly cash flow of a scene. The scope is precise enough to separate it from generic siblings like cao_bim_4d5d or cao_bim_planning_cpm, though it never names an alternative explicitly.

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 voulez la COURBE EN S DATEES" gives a clear trigger, and "action=courbe (defaut) | tresorerie" tells the agent how to pick the output mode. "debut ISO requis" flags a prerequisite. No exclusion or when-not guidance is given against the many similar BIM siblings.

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