remnawave_hosts_reorder

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

Only labels the tool as 'mutation' but does not describe side effects, permissions, or what reordering actually changes. Annotations are absent, so the description fails to compensate.

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 extremely short but sacrifices necessary information. While front-loaded, it is under-specified for a mutation tool with 4 parameters.

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?

Highly incomplete: does not explain how to reorder, what the payload should contain, the role of confirmToken and mutationApproved, or the return value. No output schema provided.

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 0% and the description provides no information about parameters (payload, confirmToken, responseMode, mutationApproved). The description adds no value beyond the schema's empty definitions.

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 states 'hosts.reorder (mutation)', which indicates it reorders hosts, but does not clarify what 'reorder' entails or how it differs from other reorder tools like remnawave_nodes_reorder. The verb and resource are present but vague.

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 guidance on when to use this tool versus alternatives (e.g., remnawave_hosts_update). No mention of prerequisites or context for reordering hosts.

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