user_telegram_webapp_auth_get

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not what the endpoint returns, not whether it establishes a session or token, not its side effects, and not rate-limit or auth requirements. The GET path prefix is the only weak signal of a read operation.

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?

It is short, but two of its four lines ('Тег: Telegram bot', 'Спека: user') are scaffolding that conveys no actionable meaning to an agent. The single informative sentence is only vaguely front-loaded, so it is under-specified rather than truly 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?

For a 4-parameter authorization endpoint with no annotations and no output schema, the description is far too thin — an agent cannot tell how to obtain initData, what a successful call yields, or how this differs from the other telegram web-auth tools.

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 100%, so the baseline is 3 per the rubric. The description adds nothing beyond the schema — it neither explains initData nor the roles of user_id, limit, and offset for this auth call.

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 an HTTP verb (GET) and resource path (/telegram/webapp/auth) plus a Russian gloss 'Авторизация Telegram', so the agent can infer this is a Telegram WebApp authorization endpoint. However, it gives no distinguishing detail versus close siblings like user_telegram_web_auth_post, user_telegram_web_auth_init_get, user_telegram_web_auth_start_get, and user_telegram_web_callback_get.

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?

There is no when-to-use guidance, no prerequisite (e.g., that initData must come from a Telegram client), and no mention of the alternative auth-flow endpoints in the sibling set. The trailing 'Тег'/'Спека' lines are catalog metadata, not usage guidance.

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