Move, trash, restore, delete or like creations

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

Beyond the annotations (mutating, destructive), the description adds critical nuance: trash is reversible, restore undoes trash, delete is permanent and requires prior trashing, batch operations are reversible, and like/unlike are idempotent setters. It also discloses the 'manage' scope requirement, which annotations do not cover.

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 a single dense paragraph but well-organized by action type. Every sentence carries necessary behavioral details, though a list format could improve skimmability. No redundant content.

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 tool has 8 actions, 4 parameters, and no output schema, this description is exceptionally complete. It covers prerequisites, reversibility, idempotency, batch limits, and the critical rule that delete only works on trashed creations. An agent has everything needed to invoke it correctly.

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 each parameter already has a clear definition. The description mostly echoes the schema (e.g., folderId supports 'root', creationId applies to all non-batch actions). No significant additional parameter meaning is provided, meriting the baseline score.

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 tool's purpose: 'Organise creations on the cloud drive' and lists all actions (move, trash, restore, delete, like/unlike, batch-trash/batch-restore). The title also enumerates these actions, making it distinct from sibling tools like manage_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?

Action-specific guidance is provided: move requires folderId or 'root', delete only works on already-trashed creations and only after explicit user request, and batch actions handle up to 100 ids. It does not compare against alternative tools, but the per-action conditions are explicit and actionable.

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