List Homey flows

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

Annotations already disclose the read-only, idempotent, and non-destructive profile, so the description does not need to repeat that. The description adds some scope context ('standard and advanced together') but no deeper behavioral details such as pagination or return shape.

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 two focused sentences: the first states the main action and scope, and the second summarizes filtering and directs to the more detailed sibling. There is 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 read-only list tool with fully documented optional parameters and clear annotations, the description is sufficient. It states what is listed, how to filter, and which sibling to use when more detail is needed.

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%, and each parameter already has a clear description. The description's 'name, folder, kind or state' maps loosely to query/folder/kind/enabledOnly/brokenOnly but does not add meaning beyond what the schema provides.

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 opens with a specific verb and resource: 'Lists the flows on this Homey' and explicitly states that standard and advanced flows are included together. It also distinguishes itself from homey_flow_get by indicating that sibling is used to see what one flow actually does.

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?

Clear context is provided for using this tool: list flows and filter by name, folder, kind, or state. The description also names homey_flow_get as the alternative for deeper detail, though it does not explicitly state when not to use this tool.

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