remnawave_snippets_create

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

No annotations are provided, and the description only states it is a 'mutation'. It does not disclose any behavioral traits such as side effects, idempotency, required permissions, or potential destructive actions. The description carries the full burden but is nearly empty.

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 (two words plus '(mutation)'), which is underspecification rather than conciseness. Every sentence should earn its place, but here there is no substantive content.

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 has 4 parameters (including a nested object), no output schema, and no annotations, the description is entirely insufficient. It does not help the agent understand what the tool does, what parameters are needed, or what to expect.

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, yet the description does not explain any of them. It fails to add meaning beyond the schema, despite the schema being minimal (e.g., 'payload' is an untyped object).

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 is 'Remnawave snippets.create (mutation)', which essentially repeats the tool name and resource. It adds no detail about what a snippet is or what creation entails, and does not distinguish from sibling tools like 'remnawave_snippets_delete' or 'remnawave_snippets_list' beyond implying it is a create operation.

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?

There is no guidance on when to use this tool versus alternatives. The description provides no context about prerequisites, typical use cases, or situations where this tool is appropriate.

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