remnawave_templates_list

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

With no annotations, the description must disclose behavioral traits. It only notes this is a read operation, but does not explain the presence of mutationApproved or responseMode parameters, pagination, filtering, or security requirements. The inclusion of a mutation-related parameter in a read tool is confusing and not clarified.

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 concise, it is under-specified. It fails to include necessary details about parameters, usage, or output, making it insufficient for an agent to use 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 4 parameters with 0% schema coverage, no output schema, and no annotations, the description is grossly incomplete. It does not explain what the tool returns, how to customize the request, or any usage context, leaving the agent with almost no useful information.

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%, so the description must compensate by explaining parameters. It does not mention payload, confirmToken, responseMode, or mutationApproved, leaving their purpose entirely unclear for a list operation.

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.list (read)' clearly states the verb 'list' and the resource 'templates', and indicates a read operation. This distinguishes it from sibling tools like create, delete, and get. However, the phrasing 'templates.list' is somewhat unusual, preventing a 5.

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 such as remnawave_templates_get or other list tools. There is no context for when listing is appropriate or what distinguishes this from similar operations.

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