remnawave_snippets_update

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

The description only says 'mutation' but provides no details on behavioral traits like required permissions, side effects, or what happens on update. With no annotations, the description carries full burden and is insufficient.

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?

While short, the description is under-specified and fails to provide useful information. It is not concise in an informative sense; it is simply minimal and vague.

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?

With 4 parameters including a nested object and no output schema, the description is severely incomplete. An agent cannot correctly determine how to call this tool.

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 adds no information about parameters. The agent gets no help understanding what 'payload', 'confirmToken', 'responseMode', or 'mutationApproved' mean or how to use them.

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 it is an update mutation for snippets, but it is generic and does not specify what aspects of snippets are updated nor distinguish from sibling tools like create or 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 on when to use this tool versus alternatives such as remnawave_snippets_create or remnawave_snippets_delete. No prerequisites or context provided.

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