Move Organize Node

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

Annotations already indicate a mutation (readOnlyHint=false) and non-destructive intent. The description adds 'Experimental' status and explicitly states it 'preserves the target document, tag, or collection' and 'changes only sidebar placement', providing useful side-effect context beyond the annotations.

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 sentences, front-loaded with the experimental warning, and every phrase adds value without redundancy. It is concise and well-structured.

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 relatively simple move operation, the description adequately covers purpose, scope, and effect on the target. With an output schema and annotations present, no major information gaps remain.

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%, so all four parameters (nodeId, parentId, index, workspaceId) are fully documented in the schema. The description does not add parameter syntax or format details, keeping it at the baseline 3.

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 ('move') and resource ('AFFiNE organize folder or link node'), and clearly distinguishes from sibling tools like move_doc by noting it changes only sidebar placement and preserves the target document, tag, or collection.

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 clear context: it is for reorganizing sidebar nodes, not moving content. It doesn't explicitly name alternatives, but the scope statement ('changes only sidebar placement') implicitly differentiates from move_doc and other sibling tools.

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