Plan selected file organization

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

With no annotations, the description carries full burden. It discloses the key behavioral trait that no files are moved, which is critical for a tool that might otherwise be assumed to be destructive. The term 'dry-run' reinforces that this is a non-mutating planning operation. It could add more detail about whether the plan is returned or saved, but for a planning tool, the core safety behavior is clearly disclosed.

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 short sentences that deliver essential information without waste. The key qualifier 'dry-run' is front-loaded, and the safety note 'It does not move files' is a valuable addition in the second sentence.

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, but the absence of an output schema and the lack of parameter explanations means the agent must infer what the plan contains and how to set 'skill' and 'targetRoot.' The description provides enough to understand the tool's role, but leaves gaps in parameter interpretation and expected return value, so it is adequate but not fully complete.

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 the description does not explain any of the three parameters. It references 'selected files,' which implicitly maps to the required selectionId, but provides no meaning for 'skill' or 'targetRoot.' The description does not compensate for the lack of schema property 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 verb 'Create' and the resource 'a dry-run folder organization plan for selected files,' which is specific and distinct from sibling tools like baidu_move_file or baidu_create_folder. The explicit statement 'It does not move files' further differentiates its purpose from adjacent file-operation tools.

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 gives clear context about when to use this tool—when you want to organize files without actually moving them, indicated by 'dry-run' and 'does not move files.' However, it does not explicitly name alternatives like baidu_move_file or state 'use this instead of move_file when you want a preview,' so there is no direct exclusion guidance.

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