Rename Folder

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

The description adds behavioral context beyond annotations by explicitly stating that the tool only changes sidebar metadata and does not rename documents inside the folder. This clarifies non-obvious side effects. Annotations already indicate non-idempotent mutation, so the description provides useful supplementary info.

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 concise sentences: the first states the action, the second clarifies limitations. No wasted words, front-loaded with key information.

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?

For a simple rename tool, the description covers what it does and its limitations. It mentions 'Experimental' and the scope of changes. No output schema exists, but the description is adequate. Could add success/error hints, but not necessary given simplicity.

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 100%, so parameters are well-documented. The description does not add new meaning beyond the schema; it implies 'name' is the new folder name and 'folderId' identifies the node, but this is already clear from parameter descriptions.

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 'rename an AFFiNE organize folder node' and distinguishes it from sibling tools like create_folder or delete_folder by specifying the scope: it only changes sidebar metadata and does not rename documents inside the folder.

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 usage for renaming folder metadata but does not explicitly state when to use this tool versus alternatives, nor does it provide conditions for when not to use it. The 'Experimental' label warns of instability but doesn't guide selection.

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