Set a new display order for VPN config profiles by specifying each profile's UUID and its target position.
Reorder config profiles by providing each profile UUID with its new position
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Array of config profiles with their new positions |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention that this is a mutating operation that overwrites ordering, whether partial arrays are allowed or all profiles must be included, or any side effects. The agent is left to infer these traits.
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 a single concise sentence with no filler, and the core action is front-loaded. It is appropriately sized for the tool's simplicity.
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?
There is no output schema and no behavioral context. The description does not explain the effect on existing positions, whether the operation is atomic, what the response looks like, or if there are constraints like requiring all profiles. This is insufficient for a mutation tool with nested parameters.
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 100% because both uuid and viewPosition have descriptions. The description merely restates the parameter intent ('new position') without adding any extra semantic detail such as uniqueness constraints, array length requirements, or ordering guarantees, so it adds no value beyond the schema.
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 clearly states the specific action (reorder) and resource (config profiles), plus the method (by supplying UUIDs with new positions). This distinguishes it from other config_profiles_* tools and from reorder tools for other entities.
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?
No explicit when-to-use or alternative guidance is provided. The tool name strongly implies it is for reordering config profiles, but the description does not state when to prefer this over related operations like config_profiles_update, nor does it mention any exclusions or preconditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.