remnawave_users_get_by_username

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

The tag 'sensitive-read' hints at special access requirements but does not elaborate on security implications, side effects, or other behavioral traits. With no annotations, the description fails to provide sufficient transparency.

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 brief (one sentence) but lacks necessary information, making it under-specified rather than appropriately 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?

Given the tool's complexity (four parameters, no output schema, many siblings), the description is dramatically incomplete. It does not explain input structure, return values, or how to invoke the tool correctly.

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 the description omits any explanation of the four input parameters, including the opaque payload object. The agent cannot determine how to specify the username or use other fields like confirmToken or responseMode.

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 'users.get_by_username (sensitive-read)', which clearly identifies the tool as retrieving a user by username. Among siblings with multiple get-by-identifier tools, this distinguishes itself by indicating the lookup key.

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 like users_get_by_email or users_get_by_id. The description lacks any context on preferred use cases or exclusions.

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