Move Collection

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

Annotations (readOnlyHint=false, destructiveHint=false) already indicate a mutating but non-destructive operation. The description adds the context that moving can target another collection or root, but does not disclose further behavioral details such as effects on child collections or permissions. No contradiction with annotations.

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?

One sentence of 14 words, front-loaded with the action 'Move a collection.' No filler or redundant information.

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 simple two-parameter tool with an output schema, the description covers the core operation and destination options. It does not explain when to use vs alternatives, but that is covered under usage guidelines. The presence of annotations and output schema reduces the burden on the description.

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's phrasing 'under another collection' and 'to the library root' helps disambiguate the role of parent_collection_id (null for root) and implies collection_id is the collection being moved. However, it does not explicitly name parameters or explain edge cases like moving into a descendant.

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 a specific verb 'Move' and clearly specifies the resource (collection) and the two possible destinations: 'under another collection' or 'to the library root.' This distinguishes it from sibling tools like rename_collection or add_to_collection.

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 implies the tool is for reorganizing collection hierarchy but does not explicitly state when to use it over alternatives or mention any prerequisites or exclusions. No when-not guidance is provided.

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