Create Folder

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

The description adds behavioral context beyond annotations by labeling the tool 'Experimental' and clarifying that it only changes sidebar organization, not document content. This goes beyond the structured annotations and helps manage expectations about side effects. It does not contradict annotations.

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 sentences, front-loaded with the key purpose, and every word adds value. It is concise without sacrificing clarity.

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?

The tool is relatively simple, has full parameter schema coverage, and an output schema exists (per context signals). The description covers the essential purpose and scope, but could mention duplicate-name behavior or error cases. Still, it is adequately complete for an experienced agent.

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 100%, so the schema already documents all four parameters. The description does not add parameter-specific meaning beyond what is in the schema, so it meets the baseline but does not elevate it.

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: 'create an AFFiNE organize folder node in the sidebar tree.' It uses a specific verb and resource, and distinguishes from sibling tools by clarifying it only affects sidebar organization, not document content.

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 implies when to use the tool by defining its scope ('create an AFFiNE organize folder node') and explicitly states what it does NOT do ('not document content'), which acts as an exclusion. However, it does not name alternative tools for document creation or other operations, so it lacks explicit alternative guidance.

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