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

Annotations already declare it is a non-read-only, non-idempotent, non-destructive create. The description adds genuine behavioral context beyond them: edges targeting missing nodes are silently dropped, nodes are auto-laid out, and the response reports flow id, node/edge counts, and dropped-edge count. That dropped-edge disclosure is exactly the kind of side effect an agent needs.

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?

Front-loaded purpose, then constraints, then return values, in four tight sentences. No filler or repetition despite covering a fair amount of ground.

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 compensates by describing the return payload (flow id, counts, dropped edges), and the drop/auto-layout semantics round out the mutation behavior. Nothing an agent needs to call this correctly appears missing.

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 100%, so the schema already documents every parameter and both enums. The description restates the node-type and edge-kind enumerations (already in the schema) and adds no per-parameter guidance, so it lands at the baseline rather than adding value.

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 ('Create a saved Wavelength flow from an explicit node and edge structure') and immediately differentiates itself from the sibling create_flow_from_text via 'with no AI call.' An agent can distinguish it from the graph-building siblings without opening the schema.

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?

'Use this when the client already has the graph' gives an explicit triggering condition that routes the agent away from the text/AI path. It stops short of naming create_flow_from_text directly as the alternative, but the 'no AI call' framing makes the boundary clear.

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