remnawave_templates_update

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

The description labels the tool as a 'mutation', indicating state change, but provides no further behavioral details such as required permissions, side effects, or implications of parameters like confirmToken and mutationApproved. With no annotations, the description carries the full disclosure burden but fails to deliver.

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 the description is very short (6 words), it is under-specified rather than concise. It lacks essential details about the tool's operation, making it insufficient for an agent to select or invoke correctly.

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 complexity (4 parameters including a nested payload object, no output schema) and the absence of annotations, the description is drastically incomplete. It does not explain what templates are, how to construct the payload, or how to use the safety parameters, leaving critical gaps.

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 meaning to any of the 4 parameters. The payload object, confirmToken, responseMode, and mutationApproved are entirely unexplained, leaving the agent to guess their roles.

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 templates.update (mutation)' merely restates the tool name with a parenthetical 'mutation'. It does not specify what templates are, what updating entails, or distinguish this from sibling tools like remnawave_templates_create or remnawave_templates_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. Sibling tools include create, delete, list, get, and reorder, but the description offers no context for choosing update over them.

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