List Organize Nodes

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

Declared 'Experimental' hints at instability but no other behavioral traits are disclosed (e.g., read-only, side effects, permissions). No annotations exist to carry the burden.

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?

Extremely concise at one sentence, but omits critical details. Conciseness here sacrifices completeness; the sentence is under-specified for reliable tool selection.

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 parameter descriptions, and no annotations, the description is severely incomplete. It fails to provide enough context for correct invocation, especially given the presence of many similar sibling tools.

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 0%, and description provides no details on the workspaceId parameter—its purpose, required status, or format. The description vaguely mentions 'from the folders workspace DB' but doesn't explicitly link to the 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 states the specific verb 'list' and resource 'AFFiNE sidebar organize nodes', distinguishing it from sibling tools like list_workspace_tree and list_children. However, 'organize nodes' is somewhat jargon-y and unclear without domain knowledge.

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 list_workspace_tree or list_children. No exclusions, prerequisites, or context provided.

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