sync_move

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

No annotations provided. The description discloses move behavior and optional empty directory cleanup but omits details like whether source files are deleted, permission requirements, error handling, or async behavior.

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?

Description is a single sentence conveying core functionality efficiently. Slightly more context could be added 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?

With 8 parameters and no output schema, the description only covers the basic operation. Missing details on parameter interplay, edge cases, and typical usage patterns.

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% with all parameters described. Description adds no additional meaning beyond the schema, meeting the baseline without further enhancement.

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 moves objects from a source to a destination, with optional empty directory cleanup. It distinguishes from siblings like sync_copy (copy) and sync_sync (sync) by using 'move' vs 'copy' or 'sync'.

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?

No explicit guidance on when to use this tool versus alternatives like sync_copy or sync_sync. The description implies usage for moving but does not provide when-not or exclusion criteria.

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