List Flows

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the return payload (flow ID, name, enabled/broken status, type) and the domain definition of flows. This is useful behavior context beyond annotations, especially 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 three sentences and each earns its place: the first states the action and scope, the second lists the returned fields, and the third defines flows in Homey context. It is front-loaded with the action and concise, with no redundant or vague wording.

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 zero-parameter, read-only list tool with no output schema, the description is complete: it states what is listed, what is returned, and what flows are. The annotation covers safety, and no additional information is needed for an agent to select and invoke this tool correctly.

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 has zero parameters, and schema description coverage is 100% (vacuously). The baseline for 0 parameters is 4. The description does not need to explain parameters because there are none; it focuses on the listing behavior and return data.

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 'List all automation flows' with the specific verb 'list' and resource 'automation flows'. It also specifies the scope ('simple and advanced') and the return fields (ID, name, enabled/broken status, type), distinguishing it from sibling tools like list_devices and list_variables. The added explanation of flows as Homey's automations with WHEN/AND/THEN logic further clarifies the resource.

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?

The description implies usage as the go-to tool for listing all flows, but it does not explicitly mention when to use this tool versus alternatives. There is no guidance about using trigger_flow or set_flow_enabled for flow actions, nor any exclusions. The context is clear enough for a simple list operation, but alternatives are not addressed.

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