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

Annotations already declare destructive=true, idempotent=false, and readOnly=false. The description adds one genuine behavioral detail beyond them — that missing destination parent directories are auto-created. However, it omits the most important mutation semantics for a destructive move: whether an existing destination is overwritten or the call fails, which the annotations do not cover.

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 the action, then the scoping constraint, then the side effect. Every sentence carries information, though the parenthetical comparison to sibling tools is slightly verbose.

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 destructive, non-idempotent mutation with no output schema, the description covers scope, the cross-root exclusion, and parent-directory creation. The main remaining gap is overwrite/failure behavior when the destination exists, which an agent would want before invoking a destructive move.

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 100%, so all four parameters are already documented, including the 'within the same root' note on `to`. The description reinforces the same-root constraint for both paths but adds no syntax, format, or edge-case meaning beyond the schema, so the baseline 3 applies.

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 pair (rename/move) and resource (file or directory on an iOS device), and explicitly distinguishes itself from ios_file_list, ios_file_pull, and ios_file_push. An agent can tell what this does and what it is not without opening any schema.

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?

Gives a clear when-not rule: cross-root moves (app container <-> shared media) must use ios_file_pull + ios_file_push instead. It also anchors the bundleId selection to ios_file_list. It does not contrast with ios_file_copy or ios_file_delete, so the routing picture is slightly incomplete, but the key exclusion is explicit.

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