Files Move Path

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

The description adds no behavioral information beyond the annotations. It does not state whether the operation renames, overwrites, moves across volumes, preserves metadata, or what happens to the source path after the move. With no readOnlyHint and only sparse annotations, this is a significant omission.

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 short but empty; this is under-specification rather than effective conciseness. It front-loads boilerplate ('Delegated Apple domain tool') instead of the actual operation. Every sentence should add value, and here neither sentence does.

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 mutating file operation with no behavioral explanation, the description is inadequate. An agent cannot determine path semantics, error conditions, overwrite behavior, or whether this is the right tool versus the many file-related siblings. The existence of an output schema does not compensate for the missing operational 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?

The input schema has 0% description coverage, so the description needed to compensate by explaining that source and destination are filesystem paths and what forms they may take. It does not. The parameter names 'source' and 'destination' are somewhat self-explanatory, but no additional semantic detail is provided.

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 only restates the tool name ('files_move_path') and labels it a 'Delegated Apple domain tool' without explaining what moving a path actually does. There is no verb, resource, or scope beyond what the title already conveys. It is essentially a tautology.

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 gives no guidance on when to use this tool versus related file tools such as files_delete_path, files_open_path, or files_list_directory. There is no mention of appropriate scenarios, preconditions, or alternatives. An agent receives no decision-relevant context.

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