Create a Homey flow

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

The description provides rich behavioral detail beyond the annotations: the flow is created switched OFF, placed in an AI folder, validated first and refused if invalid, then read back from Homey and compared for correctness. It also tells the caller the result carries a link to the flow in the Homey app, which is especially useful given there is 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?

The description is four sentences with no filler or redundancy. Every sentence contributes meaningful behavioral information: what is created, where it is placed, how it is validated, and what the result includes.

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?

The tool has a complex nested schema and no output schema, but the description covers the result link, safety behavior, and validation. It is not fully explicit about the need for prior authentication or how the caller should choose between homey_flow_create and homey_advancedflow_create, but it is otherwise complete for the most important outcomes.

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 input schema already covers all parameters with 100% description coverage, so the baseline is 3. The description itself does not add direct explanation about name, trigger, actions, or conditions as parameters, but this is unnecessary because the schema is already detailed enough.

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 "Builds a new flow," identifying the specific action and resource. It goes beyond creating to explain the flow is created switched off in an AI folder, helping distinguish it from related flow tools like update, validate, delete, and start.

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 clear usage context: the tool creates a new flow, initially disabled and placed in the AI folder for owner review. It does not explicitly mention when to use homey_flow_create over homey_advancedflow_create or homey_flow_update, but the "builds a new flow" framing is sufficient for basic selection.

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