remnawave_templates_reorder

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

No annotations are provided, so the description must disclose behavioral traits. It only labels the tool as a 'mutation' but does not describe side effects, permissions required, or what state changes occur. Crucial 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?

While concise, the description is severely under-specified. It fails to provide necessary information, making it unhelpful rather than efficiently informative.

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?

Given the complexity of the tool (a mutation with a payload and confirmation token) and the lack of output schema, the description is completely inadequate. It does not explain return values, errors, or the effect of reordering.

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?

The input schema has 4 parameters with 0% description coverage, and the description provides no explanation of the payload, confirmToken, responseMode, or mutationApproved fields. The description adds no semantic 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 states 'Remnawave templates.reorder (mutation)', which redundantly repeats the tool name. It indicates a mutation but provides no specifics about what reordering entails or what 'templates' refers to. It does not differentiate from sibling reorder tools.

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 is given on when to use this tool versus the many other reorder tools (e.g., remnawave_hosts_reorder, remnawave_profiles_reorder). There is no mention of prerequisites, context, or alternatives.

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