user_telegram_web_auth_start_get

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: this endpoint issues an HTTP redirect to Telegram OAuth rather than returning data, which matters a lot for how an agent handles the call. However, nothing is said about authentication requirements, what the redirect URL contains, or what the caller should do afterward.

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 text is short, but it is front-loaded with a raw HTTP method/path plus 'Тег' and 'Спека' metadata that contribute little decision value. The one substantive sentence (the Russian redirect description) is buried after the endpoint string.

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 no annotations, no output schema, and three parameters including counterintuitive limit/offset on an auth-start route, the description should explain the call contract, redirect behavior details, and any auth prerequisites. It leaves most of that undocumented.

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% (limit, offset, user_id are all documented inline), so the baseline of 3 applies. The description adds no parameter meaning of its own and does not explain why pagination parameters exist on an OIDC-start endpoint.

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 a specific verb and resource: starting a Telegram Login OIDC flow with an HTTP redirect to Telegram OAuth. That is enough to distinguish it from generic auth tools, but it gives no differentiation from near-identical siblings like user_telegram_web_auth_init_get or 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 guidance on when to call this versus user_telegram_web_auth_init_get, user_telegram_web_auth_post, or user_telegram_webapp_auth_get. The agent is left to infer the entry point of the flow purely from the word 'Старт'.

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