Move Document in Sidebar

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

Annotations indicate a non-read-only, non-idempotent mutation. The description adds behavioral context: if fromParentDocId is omitted, the doc is only added to the new parent, not removed from the old one. This goes beyond the annotations without contradicting them.

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?

Two concise sentences front-load the core action ('Move a doc in the AFFiNE sidebar by embedding it under a new parent') and then explain the optional parameter behavior. No superfluous text.

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 moderate complexity (4 parameters, no nested objects) and annotations covering the safety profile, the description provides enough context for correct use. No output schema is needed for a move operation, and the behavior is fully explained.

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?

With 75% schema description coverage, the description adds meaning to fromParentDocId by explaining its effect when omitted. workspaceId lacks description but is self-explanatory as a workspace identifier. The added context justifies a score above the baseline of 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 clearly states that the tool moves a doc in the AFFiNE sidebar by embedding it under a new parent. It uses specific verbs and resources, distinguishing it from siblings like delete_doc or create_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 explains the optional behavior of removing from the old parent via the fromParentDocId parameter. However, it does not explicitly state when to use this tool versus alternatives like move_organize_node, so it lacks exclusion guidance.

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