remnawave_users_get_by_telegram_id

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

The description offers a hint about sensitivity and read-only nature via '(sensitive-read)', but with no annotations, it fails to disclose behavior such as authentication requirements, idempotency, or side effects. The payload and confirmToken parameters are unexplained.

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), which is concise but sacrifices meaningful content. It does not earn its place by adding value beyond the name.

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 complexity (4 parameters, no schema descriptions, no output schema, many sibling tools), the description is woefully incomplete. It lacks essential information for correct invocation.

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 explanation for the four parameters (payload, confirmToken, responseMode, mutationApproved). The agent cannot infer how to specify the Telegram ID or interpret the other fields.

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 only repeats the function name and adds '(sensitive-read)', which hints at a read operation but does not explicitly state that this tool retrieves a user by Telegram ID. It distinguishes minimally from siblings but lacks a clear verb+resource statement.

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 get_by_email, get_by_username, etc. The agent must infer usage solely from the name.

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