remnawave_snippets_list

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

The description only says 'read', which hints at non-destructive behavior, but no annotations are provided. It lacks details about authorization requirements, side effects (if any), pagination, or rate limits. With zero annotations, the description should compensate, but it barely does.

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 (5 words), but it sacrifices essential information for brevity. True conciseness would pack useful guidance without fluff; here, the under-specification makes it ineffective, not 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 complexity (4 params including a nested object, no output schema, 0% coverage), the description is woefully incomplete. There is no mention of what the list contains, how to filter, response format, or usage patterns. For a list operation, this leaves the agent with insufficient context to invoke correctly.

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 four parameters (payload, confirmToken, responseMode, mutationApproved) with 0% coverage (no descriptions). The description adds nothing about these parameters, leaving the agent unable to understand what payload means, why a confirmToken is needed, or how responseMode affects output. This is a critical gap.

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 snippets.list (read)' essentially restates the tool name and indicates it's a read operation. It does not specify what snippets are listed, what is returned, or any scope. This is a tautology with minimal added value, barely distinguishing it from siblings like remnawave_snippets_create.

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 vs. alternatives. Among siblings, there are multiple snippets tools (create, delete, update, list), but the description offers no context about use cases, prerequisites, or when listing is appropriate. The agent is left to guess.

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