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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description must explain what state is touched; it does say 'suivi persistant' and details what structure.componentRefs and sourceHeaderRefs contain, which is genuinely additive. However it never states whether an existing session/tracking state is overwritten, what happens if expectedVersion mismatches, or whether anything is mutated on the page — notable gaps for a non-read-only tool.

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 core purpose is front-loaded in the first clause and the remaining sentences each carry operational content (graph-mode return shape, downstream read advice, restartSession rule) with little padding. Density is high and it switches between French prose and English field names, which slightly hurts scannability but not length.

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?

With no output schema, the description usefully documents the returned structure fields (componentRefs, sourceHeaderRefs), and it clarifies the enum switch via 'En mode graph'. But for a 7-parameter, non-read-only tool it leaves pagination, section scoping, and expectedVersion concurrency semantics entirely unexplained, so an agent cannot call it safely in all cases.

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% across 7 parameters, so the description carries the full burden. It only adds meaning for two of them — representation ('En mode graph...') and restartSession — leaving pageId, limit, offset, sectionIds, and expectedVersion completely unelaborated beyond their bare types.

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 verb 'Préparer' plus the resource ('une finition complète en un appel') states a specific preparation step, and the description names the concrete artifacts produced: persistent tracking, a three-zone visual plan, and a block map in three formats. It is distinguishable from nearby siblings like get_clone_review or apply_clone_repairs by being the preparation stage, though the term 'finition' is domain jargon that an agent must infer means clone polish.

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 sequencing guidance for what to do *after* calling ('Lire ces refs avec get_page_elements ... avant de reconstruire') and a restriction on restartSession ('seulement pour une nouvelle demande client'). What is missing is explicit guidance on when to call this tool rather than the many adjacent clone/structure tools (get_page_structure, get_page_blocks, get_clone_review) or any preconditions.

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