jio_move_to_album

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

With no annotations, the description carries the burden of behavioral disclosure. It clarifies that the destination must be a folder album, and that items[] metadata improves results, but it does not disclose whether the move is permanent, required permissions, or error behavior. This is helpful but not fully transparent.

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?

Two sentences with no redundancy: the first states the core action and destination, and the second provides optional parameter guidance and the alternative for board albums. Every word earns its place.

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?

The description is adequate for a move operation with no annotations or output schema. It names the resources, the optional enhancement (items[]), and the sibling alternative, which is sufficient for an agent to select and invoke the tool correctly. It lacks some depth on outcomes but overall is complete for its complexity.

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 coverage is only 33% (albumId). The description compensates by explaining items[] as 'optional' and listing relevant fields (name/objectType/sourceName), and reinforces albumId as a folder objectKey. The 'ids' parameter is left to inference, but its meaning is clear from the name and the verb 'move'.

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 uses specific action verb 'Move files or folders' and identifies the target as 'folder album by destination albumId (folder objectKey)', clearly distinguishing it from sibling jio_add_to_board which is for native board albums. This is a precise, unambiguous purpose.

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?

Explicitly instructs when to use this tool versus jio_add_to_board ('For native board albums, use jio_add_to_board instead'), and provides guidance on optional items[] with name/objectType/sourceName for best results. This gives clear when-to-use and when-not-to-use context.

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