Delete a flow folder

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

The annotations already declare destructiveHint=true, and the description reinforces this by saying 'Removes' and 'Deleting a folder never deletes a flow.' It adds useful context about the constraint that the folder must be empty and that flows are not deleted. This goes beyond the annotation, which just flags destructiveness, so it earns a 4.

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 extremely concise: three sentences, each adding value. It doesn't waste words and is front-loaded with the core action. The constraint and safety note are logically placed.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is nearly complete. It provides the key behavioral detail (empty-only constraint) and a pointer to the alternative for moving flows. It could theoretically mention error behavior, but that's not necessary for this simple tool; it earns a 4.

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 provides a description for the 'folder' parameter: 'The folder id, or its exact name.' The description adds no further parameter detail, but with 100% schema description coverage, the baseline is 3; it gets a 4 because the tool has only one parameter and the description is adequately handled by 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 the tool's purpose: 'Removes an empty flow folder.' It uses a specific verb ('Removes') and a specific resource ('flow folder'), and it distinguishes itself from sibling tools like homey_flow_delete by clarifying it deletes folders, not flows.

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 explicitly states when to use the tool: deleting an empty folder, and when not to: when the folder still contains flows, in which case the user should move them out first with homey_flow_move. It names an alternative tool and provides a clear precondition.

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