remnawave_users_get_by_short_uuid

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

With no annotations, the description carries full burden for behavioral traits. It hints at a sensitive read operation but does not disclose authentication needs, rate limits, side effects, or what data is returned. This is insufficient for an AI agent to understand the tool's behavior.

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 not concise—it lacks critical information. Conciseness should not sacrifice clarity; here it sacrifices everything.

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 (4 params, nested object, no output schema) and many siblings, the description fails to provide any contextual completeness. It does not explain return values, parameter usage, or prerequisites.

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 provides no explanation for any of the 4 parameters (payload, confirmToken, responseMode, mutationApproved). The payload object likely expects the short UUID but this is not clarified, leaving the agent confused.

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 'Remnawave users.get_by_short_uuid (sensitive-read)' is nearly a tautology of the tool name. It adds minimal context by labeling it 'sensitive-read' but fails to clearly state that the tool retrieves a user by their short UUID.

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 over sibling tools like remnawave_users_get_by_email, remnawave_users_get_by_id, etc. The description does not explain scenarios where short UUID lookup is preferred.

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