remnawave_create_host

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

Discloses that the tool mutates production and enabled hosts appear immediately in subscriptions. Annotations confirm mutation and non-idempotence; description adds value beyond annotations by specifying immediate effect and prerequisite lookup.

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 sentences: first states purpose and effect, second states prerequisite. No unnecessary words. Front-loaded with critical information.

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?

Covers purpose, effect, and prerequisite. With output schema present, return values are implicitly handled. Could mention validation constraints, but optional parameters are self-explanatory via schema. Adequate for the tool's complexity.

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 provides descriptions for all parameters (100% coverage). Description adds semantic value by explicitly noting the two required UUIDs and their relationship to remnawave_list_config_profiles, aiding parameter understanding.

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 clearly states 'Create a subscription host' with verb and resource. Explicitly distinguishes from sibling tools like remnawave_delete_host and remnawave_update_host, and provides specific context (mutates production, requires config profile & inbound UUID).

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?

Explicitly states prerequisite (config profile + inbound pair) and directs to remnawave_list_config_profiles for UUIDs. Does not mention when not to use or alternatives like update_host, but context is clear enough for typical use.

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