remnawave_revoke_user

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

DestructiveHint=true is supplemented by 'regenerating credentials' and 'old links stop working', providing clear behavioral context. No contradictions with annotations.

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 concise sentences with front-loaded purpose, no unnecessary words.

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?

Covers key behavioral impact and safety considerations. Output schema exists but description does not detail return values, which is acceptable.

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 coverage is 0% and description does not mention the uuid parameter or its role, failing to compensate for low schema documentation. However, the parameter is simple and well-named.

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?

Clearly states the action 'revoke', the resource 'user's subscription', and the outcome 'regenerating their credentials' and 'old subscription links stop working'. Distinguishes from disable/enable/user deletion.

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?

Implied usage (when needing to invalidate subscription links), but no explicit when-to-use or comparison with siblings like disable_user or delete_user.

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