folder_move_describe

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

Declares 'No side effects: read-only by contract — never mutates OmniFocus' and describes return format { description, plannedChanges }, ensuring full transparency without annotations.

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?

Three sentences front-loaded with purpose, includes usage guidance and return info. Slightly redundant example line, but overall clear and concise.

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, description adequately explains return structure ({ description, plannedChanges }) and tool's role as dry-run companion, covering all needed context.

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 covers 100% of parameters with descriptions, so baseline is 3. Description mentions 'pass the same args you would to the write tool' but adds no new semantics beyond 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?

Explicitly states 'Preview what folder_move would do without making any changes' and distinguishes from sibling folder_move by saying 'Do NOT use to actually move a folder — use folder_move instead.'

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?

Provides clear when-to-use guidance as a dry-run companion before the write tool, explicitly warns against using for actual moves, and instructs to pass same args, inspect plannedChanges, then call write tool.

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