remnawave_hosts_update

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

The description only labels the tool as a 'mutation', but without annotations, it fails to disclose important behaviors such as whether updates are destructive, if confirmation is required, or what the scope of changes is.

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 at the expense of being useless. It fails to convey necessary information, making it an under-specification rather than a concise summary.

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 (4 parameters including a loosely-typed payload, no output schema, and zero documentation), the description is woefully incomplete. An agent cannot determine how to construct a valid request or what to expect in return.

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 provides no explanation of the parameters. The payload object's structure is undefined, and none of the four parameters are described, leaving the agent without guidance on how to invoke the tool correctly.

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 'hosts.update (mutation)', which identifies the verb (update) and resource (hosts), but it lacks specificity about what aspects of hosts are updated and how it differs from sibling tools like remnawave_hosts_bulk_update.

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 usage guidelines are provided. The description does not indicate when to use this tool versus its siblings, nor does it mention any prerequisites or context.

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