remnawave_hwid_list_users

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

No annotations provided. The description labels it 'sensitive-read', hinting at read-only behavior, but the presence of parameters like 'mutationApproved' and 'confirmToken' could suggest mutation capabilities, creating ambiguity. No side effects or permissions are disclosed.

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 but lacks substance. It fails to convey essential information, making it under-specified rather than concise.

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 4 undocumented parameters, no output schema, and no annotations, the description is wholly insufficient. It does not cover tool behavior, return values, or parameter details.

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%, yet the description does not explain any of the 4 parameters (payload, confirmToken, responseMode, mutationApproved). Agents cannot infer their meaning or usage.

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 hwid.list_users (sensitive-read)', indicating it lists users, but it does not clarify what 'hwid' refers to or differentiate this from many sibling tools like 'remnawave_users_list' that also list users. The purpose is vague.

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. With many sibling tools listing users, the description provides no criteria for selection.

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