Create a Homey advanced flow

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

The description discloses several non-obvious behaviors: the flow is created switched OFF, placed in the 'AI' folder, and read back/compared after creation. It also explains that labels are replaced with real generated ids and references are rewritten, going beyond what the annotations (all false) or schema reveal.

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 description is dense but every sentence delivers important information: graph model, labeling behavior, token syntax, standard-flow difference, and creation side effects. No filler or redundancy.

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 complex graph-creation tool, the description covers the core model, label/token mechanics, and post-creation verification, and the schema thoroughly documents card fields. However, since there is no output schema, a brief mention of what the tool returns (e.g. the created flow or comparison result) would make it fully complete.

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 schema covers 100% of parameters, so the baseline is 3; the description adds extra meaning by explaining how to reference card outputs with the advanced-flow token syntax and clarifying that card labels are placeholders replaced by real ids. This is meaningful guidance beyond the raw schema, though much of the card structure is already documented in the schema.

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 clearly states it creates an advanced Homey flow and distinguishes it from a standard flow by defining it as a graph of cards with branches, parallel paths, joins, delays, and error handlers. The title and description use a specific verb (create) and resource (advanced flow), making it distinct from sibling homey_flow_create.

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 implies when to use this tool by contrasting advanced flows with standard flows and explicitly noting that the [[owner|token]] syntax from standard flows will not work here. It does not name the sibling tool homey_flow_create directly, but the distinction is clear enough for an agent to choose between them.

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