file_organize_apply

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly states that target conflicts are skipped and no physical deletion occurs, adding safety and execution context. It also notes the preview/adjudication requirement, which is helpful for understanding side effects.

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 concise sentence that front-loads the primary action followed by important conditions. Every clause adds value: execute move, preview prerequisite, conflict skip, and no deletion.

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 mutation tool with an output schema, the description covers essential preconditions and side effects, including conflict handling and deletion policy. The term 'adjudication' is domain-specific and not elaborated, but given the sibling preview tool, the context is sufficiently 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?

The description does not elaborate on the 'path' or 'rules' parameters, and the schema provides no descriptions for them (0% coverage). The agent must infer that 'path' is the directory and 'rules' come from preview, but the description itself lacks parameter-level detail or format guidance.

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 function: '实际执行归档移动' (actually execute archive move), which is a specific verb+resource. It distinguishes itself from siblings like file_organize_preview and file_clean_apply by emphasizing the execution step and prerequisite of preview/adjudication.

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 provides a clear usage prerequisite: '需先 preview 且通过裁决' (must preview first and pass adjudication), telling the agent when this apply tool is appropriate. It does not explicitly name alternatives or exclusions, but the prerequisite context is sufficient to guide usage.

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