user_telegram_web_callback_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates an OIDC code-flow callback, suggesting authentication-related side effects, but it does not say what happens on invocation, whether it requires special auth, whether it mutates state, or what constraints apply.

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 brief and contains little obvious bloat, but it is under-specified rather than truly concise. The mixed route, purpose, and metadata lines are not structured to front-load the most useful invocation context.

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 and no output schema, the description should compensate by explaining auth behavior, side effects, and invocation context. Instead it only names the endpoint and flow, leaving important behavioral details absent for an authentication callback tool.

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 input schema already documents limit, offset, and user_id with sufficient clarity. The description adds no parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 route and identifies the resource as a Telegram Login callback endpoint using the OIDC code flow. It is clearer than a tautology, but it does not distinguish this callback from sibling Telegram auth tools such as user_telegram_web_auth_init_get or user_telegram_webapp_auth_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?

The description gives no explicit guidance on when to call this tool versus alternatives, nor does it state prerequisites or exclusions. The only implied usage is that it is a callback endpoint, which an agent must infer on its own.

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