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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses that nothing is published, that requestId must be reused (idempotency/retry behavior), and that the result drives a mandatory control/correction workflow. These are meaningful behavioral facts entities wouldn't get from the annotation block.

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?

Five short sentences, front-loaded with the sequencing constraint and the safety note ('Ne publie rien'), with no filler. The telegraphic style is efficient, though some clauses read as compressed notes rather than full explanations.

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?

There is no output schema, and the description only hints that the result yields a mandatory review/correction workflow. Given a nested metadata requirement and a version-guard parameter, the description is adequate for orientation but leaves meaningful gaps an agent must discover from the schema alone.

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% with 6 parameters including a nested metadata object, so the description must carry the load. It only explains origin's two enum values and the requestId reuse rule; pageId, expectedPageVersion (concurrency semantics), visibility, and the required metadata fields (name, category, categoryId) are left entirely undocumented.

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 names a specific action (copying a captured page into an independent template draft) and pins down the resource ('brouillon de modèle'), distinguishing it from publishing via 'Ne publie rien'. It also anchors it to the preceding capture steps (import_html_page/clone_page_in_outil), so an agent can place it in a workflow. Slightly indirect phrasing keeps it from a 5.

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 states clear preconditions: use after import_html_page/clone_page_in_outil, with origin=browser requiring proof of capture and origin=native reserved for original composition. It lacks an explicit statement of when NOT to use it or a direct pointer to a sibling alternative (e.g. publish_template), but the sequencing guidance is strong.

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