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 and the bar is lower. The description adds domain semantics (parallel runs both branches then waits; condition selects one path) but says nothing about what the tool actually returns, whether the output is static documentation or introspected live config, or any limits in output size. That is a meaningful remaining gap for a describe tool with no output schema.

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?

Three dense sentences with no wasted filler, but the ordering is poor: the second and third sentences explain how to author workflows, which is tangential to a describe tool and pushes the actual scope statement out of focus. The parallel/condition detail belongs to a creation or simulation tool, not this one.

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 parameters, no output schema and read-only annotations, the description's main remaining duty is to say what information a caller gets back and how it differs from describe_automation; it does neither. It conveys the workflow model reasonably well but leaves the return contract and sibling differentiation unaddressed.

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 for the description to disambiguate; baseline is 4. The explanation of workflow constructs (yes/no branches, parallel vs condition) is contextual rather than parameter-related, which is acceptable here.

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 first sentence names the resource ("moteur de workflows visuels") and enumerates what it covers (triggers, actions, decisions, limits), so the agent can tell this is a documentation/describe tool for workflows. However, it never states the verb clearly (describe/explain), and the following sentences drift into how to create/modify workflows, blurring what the tool itself does. It is not a tautology, but the purpose is only loosely bounded.

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 does route mutations away by naming create_record/update_record for creating or modifying automations, which implies this tool is for reading/understanding only. But it gives no explicit condition for calling this versus the very similar sibling describe_automation, nor when a describe call is preferable to just listing workflows. Usage is implied rather than stated.

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