Reorder folders

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

Annotations already indicate a non-read-only, idempotent, non-destructive mutation. The description adds a meaningful side effect: folders without an existing metadata row are created. It does not fully describe whether unspecified siblings are untouched, but it goes beyond annotation basics.

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?

Three short sentences, with the key side effect stated after the main purpose. The opening 'Reorder folders' is slightly redundant with the title, but the remaining sentences are dense and useful.

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 single-parameter, low-complexity mutating tool, this is nearly complete: it covers purpose, usage context, and the important auto-creation behavior. It could be stronger if it described the exact expected contents of the positions payload, though the schema largely covers that.

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 must compensate, and it only partially does. It establishes that multiple sibling folders are assigned manual sortOrder values, aligning with the 'positions' array, but it does not explicitly describe expected item shape (name plus integer sortOrder) beyond what the schema property names already imply.

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?

Description identifies a concrete operation: reordering folders by setting a manual sortOrder for sibling folders. It names the mechanism (drag-to-reorder in sidebar's manual sort mode) and distinguishes it from sibling tools like reorder_hosts.

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 usage context is explicit – this is for sidebar manual-sort drag-to-reorder. It does not explicitly state when not to use it or name alternatives, but the folder-versus-host distinction in sibling names and the manual-sort context make selection clear.

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