hosts_reorder

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

Annotations already state readOnlyHint=false and destructiveHint=false, lowering the bar, but the description adds nothing about behavior: it does not say whether the provided list must be complete, what happens to hosts omitted from the array, or whether the operation is idempotent. For a mutation that rewrites ordering state, that context is missing.

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?

Two words are obviously short, but this is under-specification rather than true conciseness; nothing is front-loaded because nothing is said. It earns no place beyond echoing the name.

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 mutation tool with no output schema, 0% parameter coverage, and a nested object whose semantics matter (viewPosition), the definition is insufficient. An agent cannot confidently construct a correct call from this alone.

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% and the description offers no explanation of the single hosts parameter or its nested uuid/viewPosition fields. The critical semantic question, whether viewPosition must be a contiguous full ordering and whether the array must include all hosts, is left entirely undocumented.

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?

"Reorder hosts" restates the tool name with no additional specificity: no mention of what ordering means (viewPosition), whether it applies globally or per scope, or how it differs from siblings like nodes_reorder or squads_reorder. It names a verb and resource, so it is not fully misleading, but it is effectively a tautology of the name.

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?

There is no when-to-use guidance, no prerequisites, and no reference to alternative tools (e.g., hosts_update) for adjusting host attributes. The agent must infer purpose entirely from the name.

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