Reorder hosts

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

The description adds behavioral context beyond annotations by explaining that it sets sortOrder, restricts to hosts within the same folder, and ties to manual sort mode. With annotations already covering readOnlyHint=false, idempotentHint=true, and destructiveHint=false, this is sufficient. No contradiction.

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 concise: two sentences, no filler. The first sentence states the action, and the second provides the essential context. It is front-loaded with the verb and resource, making it easy to scan.

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 low-complexity tool with a simple array parameter and no output schema, the description offers adequate context: it explains the purpose, scope (same folder), and UI scenario. It lacks details about return behavior or prerequisites (e.g., folder existence), but given the simplicity and existing annotations, these are minor gaps.

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. It mentions 'sortOrder' and 'multiple hosts', giving some meaning to the positions array, but it does not explicitly clarify that each position object contains an 'id' (host identifier) and a 'sortOrder' value. The agent is left to infer details from the field names, which is partially aided by the description but not fully.

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 a specific verb ('reorder') and resource ('hosts'), and explains that it sets manual sortOrder values for hosts within the same folder. This distinguishes it from sibling tools like termix_hosts_reorder_folders by explicitly mentioning hosts and the context of manual sort mode.

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 provides clear context for when this tool is used: 'used by drag-to-reorder in the sidebar's manual sort mode.' This gives an agent a strong signal about the intended scenario, though it does not explicitly name alternatives or state exclusions (e.g., 'use reorder_folders for folders').

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