remnawave_templates_get

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

The only behavioral trait mentioned is 'read', which implies no side effects. With no annotations, the description should disclose more, such as required permissions, whether payload is needed for identifying a template, or response format. It fails to do so.

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 very short but lacks substantive information. It is under-specific rather than concise, failing to earn its place with useful details.

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 0% schema coverage, no annotations, no output schema, and four parameters, the description is severely incomplete. It does not explain what 'templates' are, how to specify which template to get, or what the tool returns.

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 does not explain any of the four parameters (payload, confirmToken, responseMode, mutationApproved). Their purpose and usage remain entirely unclear.

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 'Remnawave templates.get (read)', clearly identifying the action (get) and resource (templates), and indicating read-only behavior. It distinguishes from sibling tools like create/delete/list by implying retrieval of a single template, though not explicitly.

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_list or remnawave_templates_get (if other get variants exist). There are no prerequisites or context for use.

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