keygen_generate_key

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

With no annotations, the description carries the full behavioral burden. It does not say whether this generates a brand-new secret (potentially invalidating previously issued node keys) or simply returns the existing one, nor does it state required permissions or whether the operation is safe/idempotent despite the 'generate' name.

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?

Two short lines with no padding, though the raw endpoint 'GET /api/keygen' and the 'Tags: Keygen Controller' metadata are noise that precedes the actual purpose, so the useful content is not fully front-loaded.

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?

With no annotations and no output schema, the description is the only source of behavioral truth, yet it omits the key questions for a key-material endpoint: is this a read or a rotation, what is returned, and does calling it affect existing nodes. That is a meaningful gap for a 0-param 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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema. The baseline for a parameter-less tool applies.

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 names a specific verb and resource: it turns 'GET /api/keygen' into 'Get SECRET_KEY for Remnawave Node', so an agent knows it retrieves a secret key for a node. However, it does not differentiate from the similarly named sibling system_get_x25519_keypairs, which is also about retrieving cryptographic keys.

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?

There is no guidance on when to call this versus alternatives such as system_get_x25519_keypairs, no prerequisites, and no stated context. The agent is left to infer usage entirely from the one-line purpose.

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