remnawave_hosts_create

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

With no annotations, the burden is on the description to disclose behavioral traits. The word 'mutation' implies a write operation, but there is no detail on side effects, required permissions, rate limits, or what happens to existing hosts. This is severely lacking.

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 short but not effectively concise; it sacrifices useful information. It does not earn its place as it provides little value.

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 tool's mutation nature with a complex nested payload, no output schema, and absence of annotations, the description is completely inadequate. It fails to provide necessary context for correct invocation.

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. The description adds no meaning to the 'payload', 'confirmToken', 'responseMode', or 'mutationApproved' parameters. The 'payload' is a vague object with additionalProperties, leaving the agent guessing its structure.

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 'Remnawave hosts.create (mutation)' indicates a mutation action but does not clarify what a host is or what creating entails. It barely restates the tool name and fails to distinguish from sibling tools like remnawave_hosts_update or remnawave_hosts_delete.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or conditions under which this tool should be invoked.

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