remnawave_users_revoke_subscription

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

No annotations are provided, so the description carries the full burden. It only labels the tool as a 'mutation' but fails to disclose side effects like whether the subscription link is invalidated, if it affects user status, or if it is reversible. The presence of confirmToken and mutationApproved parameters hints at required approval, but this is not explained.

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 (one line), but it sacrifices essential information. It is not well-structured; a tool description should be concise yet informative. This is under-specification, not effective conciseness.

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 no annotations, no output schema, and zero parameter descriptions, the tool description is critically incomplete. An AI agent lacks sufficient context to select or correctly invoke this 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?

Schema description coverage is 0%, and the description provides no information about any of the four parameters (payload, confirmToken, responseMode, mutationApproved). The agent cannot infer their meaning or usage from the description.

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 it is a 'mutation' and the name suggests revoking a subscription, but it does not specify what revoking entails (e.g., disabling access, removing subscription URL). Compared to siblings like remnawave_users_disable, the purpose is ambiguous.

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 versus alternatives such as remnawave_users_bulk_revoke_subscription or remnawave_users_disable. There is no context on prerequisites or conditions.

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