Move Organize Node

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

No annotations are provided, so the description bears full responsibility. It fails to disclose whether the move is destructive, what happens to children, permission requirements, or side effects. The only behavioral clue is 'Experimental', which hints at instability but isn't sufficient.

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 very short (one sentence) and front-loaded with 'Experimental'. While concise, it omits essential details, making it less useful. Every word earns its place, but the overall brevity sacrifices completeness.

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?

With no output schema, no annotations, and 4 parameters, the description is critically incomplete. It doesn't explain return values, error conditions, or behavior in edge cases (e.g., moving to root vs. folder). The agent lacks enough context to use this tool safely.

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 coverage is 50% (parentId and index have descriptions, workspaceId and nodeId do not). The description adds no parameter information beyond what's in the schema, failing to compensate for the missing descriptions.

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 action 'move' and the resource 'AFFiNE organize folder or link node', which distinguishes it from sibling tools like 'add_organize_link' or 'delete_organize_link'. The 'Experimental' label adds relevant context.

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?

No guidance on when to use this tool versus alternatives like 'move_doc' or 'create_folder'. There is no mention of prerequisites, when not to use, or why you would choose this over other move-related tools.

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