Move iCloud File

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

Annotations indicate destructiveHint: true, confirming the tool mutates state. However, the description adds no behavioral context beyond that—no mention of whether overwriting occurs, whether the source is deleted, or any error handling. With annotations already flagging destructiveness, the description contributes little.

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, front-loaded sentence with no fluff, achieving conciseness. However, it is under-informative—could include brief parameter hints without becoming verbose. 3 is appropriate for being clean but insufficiently detailed.

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's complexity (move operation), the absence of parameter descriptions, and only a destructiveHint annotation, the description is incomplete. It omits path format, rename behavior, overwrite behavior, and return value (despite an output schema existing). The agent is left with critical unknowns.

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 0%, yet the description fails to explain the src and dst parameters (e.g., path formats, allowed values, or whether dst can be a directory). The agent receives no semantic guidance beyond the parameter names, resulting in a severe gap.

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 'Move or rename a file in iCloud Drive' clearly states the verb (move/rename) and resource (file in iCloud Drive). It effectively distinguishes from sibling tools like icloud_delete, icloud_write, and icloud_list, which serve different purposes.

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 no guidance on when to use this tool versus alternatives (e.g., copy or overwrite), no prerequisites (e.g., source file must exist), and no explicit exclusions. The agent must infer usage solely from the name.

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