user_telegram_user_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. It implies a read via 'GET'/'Получить' but says nothing about permissions, whether user_id defaults to the caller, pagination behavior, or what 'settings' actually contains. For a zero-annotation tool this is a significant gap.

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 short, but 'Тег: Telegram bot' and 'Спека: user' are meta boilerplate that add little for an agent choosing a tool, and the mixing of the raw HTTP verb with the natural-language line is slightly redundant. It is front-loaded with the endpoint, which helps.

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 only a one-line purpose statement, the definition does not convey enough for an agent to invoke confidently — the meaning of 'user settings' and the role of user_id ('admin acts on behalf of this user') are left entirely to the schema.

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% and all three parameters (limit, offset, user_id) are documented in the schema itself, so the baseline of 3 applies. The description adds no additional meaning about the parameters beyond the schema.

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 ('Получить' = get) and resource (Telegram bot user settings), and the HTTP path 'GET /telegram/user' reinforces the read intent. It is clearly distinguishable from the sibling write/delete variants (user_telegram_user_post, user_telegram_user_delete), though the surrounding 'Tag'/'Spec' boilerplate dilutes it slightly.

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 on when to use this tool versus alternatives. It does not mention the sibling post/delete Telegram user tools, nor does it state prerequisites such as whether admin rights or a specific user_id are needed.

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