nuvio_reorder_collectionsSet the order of collections by providing each collection ID once in the desired sequence. Reorders safely with a snapshot to allow undo if needed.
Set collection order. Provide every collection id exactly once, in the desired order. The previous state is snapshotted before the write; revert with nuvio_undo.
| Name | Required | Description | Default |
|---|---|---|---|
| profile_id | No | ||
| ordered_ids | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful behavioral context beyond annotations by disclosing that the previous state is snapshotted before the write and that the operation can be reverted with nuvio_undo. This is especially useful given readOnlyHint=false and no destructive hint.
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 compact and front-loaded. Three short sentences deliver the core action, the exact input requirement, and the undo behavior with no filler.
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 covers the essential contract: what the tool does, how ordered_ids must be provided, and how to revert. It lacks explicit mention of profile_id's role and does not reference how to obtain the collection id list, but the tool remains usable with schema clues and sibling tools.
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?
With 0% schema description coverage, the description must compensate. It nicely explains the required 'ordered_ids' parameter as a complete ordering of every collection id exactly once, but it does not explain 'profile_id' or how it scopes the reorder, leaving one parameter under-specified.
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 states a clear verb-resource pair: 'Set collection order' and explains the desired effect. It is distinguishable from sibling reorder tools by naming 'collections' specifically, though it does not explicitly contrast with nuvio_reorder_collection_folders.
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?
It gives clear operational guidance: provide every collection id exactly once in the desired order. It does not name alternatives or explicitly state when not to use it, but the context is clear enough for selection among sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.