remnawave_templates_delete

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

The description labels the tool a 'mutation' but provides no details about what gets destroyed, authorization requirements, irreversibility, or side effects. With no annotations, the description fails to disclose critical behavioral traits.

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, but this conciseness comes at the cost of informativeness. It could be longer to include necessary context while remaining efficient.

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 lack of schema descriptions, no output schema, and a mutation tool with 4 parameters, the description is wholly inadequate. It provides no information about return values, error conditions, or how to safely invoke the 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?

With 0% schema description coverage and no parameter details in the description, the agent receives no help understanding the four parameters. 'payload' is an untyped additionalProperties object, and 'confirmToken', 'responseMode', 'mutationApproved' have no explanation.

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.delete (mutation)' merely restates the tool name and action. It does not clarify what templates are being deleted or provide any distinguishing context beyond the verb 'delete'. This is a tautology.

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 given on when to use this tool versus its siblings (e.g., remnawave_templates_create, remnawave_templates_update). There is no mention of prerequisites, when not to use, or alternative tools.

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