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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine domain semantics, notably how parallel branches behave (type parallel, yes=branch A, no=branch B, wait for both before continuing), but says nothing about the shape, depth or size of the documentation actually returned, which is the key behavior for a describe 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?

All content is relevant, but it is delivered as one long semicolon-chained sentence that mixes triggers, message features, step types and sibling-tool routing without structure. The 'distincts des automations marketing' qualifier and the save_flow rule sit early, which is good, but the feature dump would scan far better as a short list.

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 no-parameter, read-only reference tool this covers the essentials: what domains are documented, the parallel-branch semantics that are easy to get wrong, and where to go next (save_flow to write, list_records/get_record to read). Only the return format and any limits on the documentation are left unstated, and no output schema exists to supply that.

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?

The tool takes zero parameters, so there is nothing the description must disambiguate; the baseline of 4 applies. The description correctly avoids inventing parameter talk and instead spends its words on what the tool covers.

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 conveys that this tool documents the general-purpose automation engine (triggers, messages, JSON steps, conditions, parallel branches, loops, HTTP, resources, tasks, agents) and explicitly separates it from marketing automations. It never states in one clause 'returns the automation capability reference,' but the enumerated topic list plus the 'Lire avant save_flow' framing makes the resource and its scope unmistakable.

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 ordering rule — read this before save_flow — which is real when-to-use guidance tied to a named sibling. It also redirects to list_records/get_record for reading existing flows, agents and tasks, and distinguishes itself from marketing automations. There is no explicit 'do not use this for X' beyond the marketing-automation contrast.

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