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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses a key constraint (both paths inside the same root/bundleId selection) and a side effect (missing parent directories are created). It does not mention overwrite behavior or what happens to the source after a move, but move is semantically standard and the disclosed behaviors add meaningful context.

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, each earning its place: the primary purpose, the cross-root exclusion with named alternatives, and the auto-creation side effect. It is front-loaded with the action and scoped precisely. No wasted words.

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 tool with no output schema or annotations, the description explains the critical operational constraints (same-root requirement, auto-creation of parent directories) and points to ios_file_list for bundleId semantics. Minor gaps exist, such as overwrite behavior on the destination and whether directories are moved recursively, but these are not essential for correct invocation.

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%, with parameters like `to` already documented as "Absolute destination path within the same root." The description reiterates the same-root constraint but adds little beyond the schema. Per the rubric, baseline 3 applies when the schema does the heavy lifting, and it does here.

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?

Description states a specific verb and resource: "Rename or move a file or directory on an iOS device." It further distinguishes itself from sibling tools by explicitly noting that cross-root moves are handled by ios_file_pull followed by ios_file_push, not this tool. This clarity separates it from related file operations like copy, delete, and stat.

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 explicitly states when this tool is NOT appropriate: "moving between an app container and the shared media directory is an ios_file_pull followed by an ios_file_push, not this." It also implies the correct use case by constraining both paths to the same root. This is clear routing guidance with named alternatives.

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