homey_run_advanced_flow

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states the action 'Trigger a specific Advanced Flow' and does not explain side effects, asynchronous execution, permissions, or what the tool returns, leaving major behavioral aspects undisclosed.

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 a single concise sentence, 'Trigger a specific Advanced Flow.' There is no fluff, repetition, or irrelevant detail, making it optimally concise and front-loaded.

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 simple one-parameter tool, the description is minimally functional but lacks important context. It does not explain the difference from 'homey_run_flow', how to retrieve the flow ID, or the outcome of triggering, and there is no output schema or annotations to compensate. This is adequate but not 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 provides 100% coverage by documenting the single 'id' parameter with 'The ID of the flow'. The description adds the word 'specific' and calls it an 'Advanced Flow', but does not offer additional format, provenance, or usage detail beyond the schema, so the baseline 3 is appropriate.

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 uses a specific verb 'Trigger' and a clearly identified resource, 'a specific Advanced Flow'. This distinguishes it from sibling tools like 'homey_run_flow' by explicitly naming the 'Advanced' variant, making the tool's function immediately understandable.

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 provides no guidance on when to use this tool instead of alternatives such as 'homey_run_flow'. It also does not mention that the flow ID would likely need to be obtained from 'homey_list_advanced_flows', leaving usage context entirely implicit.

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