Move Organize Node

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

No annotations are provided, so the description must carry the burden. It only says 'Experimental' and 'move', but does not disclose if the operation is destructive, reversible, requires authentication, or how it affects associated data. This omission is critical for a mutation tool.

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 sentence, which is concise. However, the brevity comes at the cost of missing important information. It is not verbose, but the structure could be improved to include more value without being longer.

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 4 parameters, no output schema, and no annotations, the description is far too minimal. It does not explain the return value, error conditions, or behavioral details like what happens to child nodes. It is incomplete for practical use.

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 50% (only parentId and index have descriptions). The description does not add any extra meaning for the parameters, leaving workspaceId and nodeId undocumented. It fails to compensate for the low schema coverage.

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). It is specific enough to understand what the tool does, though it does not differentiate from sibling tools like 'add_organize_link' or 'delete_organize_link'.

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. The description does not state prerequisites, context for moving, or when not to use it. The 'Experimental' tag hints at instability but does not provide usage direction.

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