Move Document in Sidebar

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

No annotations provided, so the description carries full burden. It explains the core behavior (embedding and optional removal) but does not disclose potential side effects, prerequisites, or what happens to the doc's original location beyond the optional removal.

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 succinct sentences. The first states the purpose, the second adds critical nuance. No unnecessary words.

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 complexity of a move operation and the absence of annotations and output schema, the description adequately explains the action and optional behavior. It could mention error conditions or prerequisites, but remains reasonably complete.

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?

Input schema covers 3 of 4 parameters with descriptions (workspaceId missing). The tool description adds value by explaining the conditional behavior of 'fromParentDocId' and the overall action, but does not compensate for the undocumented workspaceId parameter.

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 identifies the action (move), the resource (doc), and the context (AFFiNE sidebar). It specifies embedding under a new parent, which distinguishes it from other tools like 'move_organize_node' or 'duplicate_doc'.

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 on when to use this tool and the effect of omitting 'fromParentDocId'. It does not explicitly mention alternatives or when not to use, but the guidance is sufficient for typical use.

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