remnawave_update_host

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

Description reveals key behavioral traits beyond annotations: that it mutates production and directly affects user subscriptions. The statement about tags/nodes replacing their whole set is a clear side-effect detail not captured in annotations. Annotations already indicate mutability and idempotency, but the description adds production impact context.

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 concise sentences with no wasted words. Front-loaded with the critical mutation warning, followed by behavioral specifics. Perfectly structured for quick comprehension.

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 (many optional fields, production impact), the description covers the essential: update action, production mutation, replacement behavior for tags/nodes. Lacks explicit mention of confirmation or rollback, but with an output schema present, return values are covered. Could note prerequisites or failure modes.

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 schema provides individual parameter descriptions, so the description adds only marginal value. It explicitly notes that tags and nodes replace (not merge) their sets, which is helpful nuance. However, for other parameters, it offers no additional semantics 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 clearly states the tool updates a host and specifies the verb 'Update' with the resource 'host'. It distinguishes from siblings like remnawave_create_host and remnawave_delete_host by focusing on modification. The added warning 'MUTATES PROD' reinforces the scope.

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 explicit guidance on when to use this tool versus alternatives (e.g., create or delete). Usage is implied by the name and required UUID parameter, but missing direct comparisons or when-not scenarios.

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