user_telegram_bot_by_template_post

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 whether the POST causes side effects, not auth requirements, not idempotency, not what happens on repeated delivery. The one genuinely behavioral fact available (the confirm/preview semantics for non-GET calls) lives only in the schema, not the description.

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 and front-loads the route, but roughly half the text is metadata boilerplate (Тег: Telegram bot, Спека: user) that consumes space without helping an agent decide or invoke. Not wasteful enough to be penalized heavily, but not tight prose either.

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 POST tool with a nested body object, no output schema, and no annotations, the description is far too thin — it supplies neither side-effect information nor any hint about what the body should contain or what is returned. The schema covers parameters, but the operational context is missing.

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 four parameters are documented in the schema, including confirm's preview semantics and user_id's impersonation meaning. The description only restates the template path variable already implied by the route, so baseline 3 applies.

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 names an HTTP method and path (POST /telegram/bot/{template}) and glosses it as "Приём данных от Telegram", so an agent can infer it is a Telegram webhook-ingest endpoint. However, it never says what it does with the received data, what the template selects, or how it differs from siblings like user_telegram_user_post or user_telegram_web_callback_get. Purpose is identifiable but vague beyond the raw route.

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 or when-not-to-use guidance, no mention of prerequisites, and no routing to any alternative among the many telegram/user tools. The only usable signal is the implicit 'this is the endpoint Telegram calls', which the agent must infer from the path.

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