Rename Folder

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

No annotations are provided, and the description only says 'Experimental' without disclosing any behavioral traits such as whether the renaming is destructive, reversible, or requires specific permissions. The description fails to add necessary context.

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 short and front-loaded, but it is too brief, lacking enough substance despite its conciseness. It could be expanded to include more detail without losing conciseness.

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 no output schema, no annotations, and minimal description, the tool definition is incomplete. It does not explain return values, side effects, or usage context, leaving significant gaps for an agent to correctly invoke the tool.

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?

The input schema has three parameters with 0% schema description coverage, and the description does not explain what each parameter (e.g., workspaceId, folderId, name) represents or how they relate to the renaming operation. The description adds no meaning beyond the schema.

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 'rename an AFFiNE organize folder node' which is a specific verb+resource, clearly distinguishing from sibling tools like create_folder, delete_folder, and move_organize_node.

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 contains 'Experimental' hinting at caution but provides no explicit guidance on when to use vs alternatives or any prerequisites. No exclusions or context for appropriate usage.

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