Rename a folder or move it

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

Annotations indicate a non-readonly, non-destructive mutation, and the description adds reassuring behavior: 'The flows in it are untouched and keep working.' This adds meaningful behavioral context beyond the annotations, though it does not disclose potential errors or permission requirements.

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 concise sentences with no filler. It front-loads the core action, then adds key behavior and a specific usage nuance, every sentence contributing useful information.

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 tool's moderate complexity, the description covers the essential operation, non-destructive nature towards flows, and top-level move behavior. It omits details like duplicate-name handling or invalid-parent errors, but the schema and annotations fill in enough context for most invocation scenarios.

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 already provides 100% coverage for the three parameters, so the description need not repeat the semantics. It adds only an operational hint about parent null moving a folder to top level, which is also in the schema. Thus a baseline score of 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 clearly states the tool's dual purpose: 'Renames a flow folder, moves it inside another one, or both.' It also distinguishes itself from sibling tools like homey_flow_folder_create/delete and homey_flow_move by focusing on folder update operations.

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 practical usage context, such as 'Send parent as null to move a folder back to the top level,' making the move behavior explicit. It does not explicitly mention when not to use it or name alternatives, but the context of 'update folder' is clear enough for a competent agent.

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