icloud_rename

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It does not say whether an existing target name is overwritten, whether the operation fails on collision, what permissions are required, or whether the change is reversible. The presence of an output schema only relieves it of describing return values.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the extreme terseness is achieved partly by omitting necessary detail rather than by editing it out.

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 no annotations, zero parameter documentation, and a sibling (icloud_move) that plausibly overlaps, one sentence is not enough. The output schema covers returns, but nothing addresses collision behavior, permissions, or path conventions.

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%, so the description must compensate and it does not. It gives no guidance on path format (absolute vs. relative to iCloud Drive root, whether folders use a trailing separator) or naming constraints for new_name, leaving the two required parameters entirely unexplained beyond their self-evident titles.

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?

States a specific verb (rename) and resource (file or folder) with the scoping qualifier 'in place'. This distinguishes it implicitly from location-changing operations, though it never names the icloud_move sibling that is the closest alternative.

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?

'In place' implies the name changes but the location does not, which faintly signals when to prefer this over icloud_move, but no alternative or condition is stated explicitly. An agent must infer the rename-vs-move boundary on its own.

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