telegram_test_connection

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

With no annotations provided, the description carries the full burden. It usefully discloses that the tool verifies credentials, session connectivity, and authorization, implying a diagnostic/read-only check. However, it does not state side effects, network behavior, or how failures are returned, leaving some behavioral ambiguity.

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?

A single, front-loaded sentence with no filler. Every phrase adds meaningful scope: credentials, StringSession, and authorization all specify what the connection check covers.

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 zero-parameter connectivity test with an output schema present, the description is complete. It names all key preconditions (credentials, session, authorization) and the tool's simple purpose requires no further explanation.

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?

The tool has zero parameters, so the baseline is 4. The description correctly omits parameter details because there are none to document, and the empty input schema leaves no ambiguity.

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 ('check') and the exact resources checked: Telegram credentials, StringSession connectivity, and account authorization. This clearly distinguishes it from sibling test_connection tools such as dart_test_connection and toss_test_connection.

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 makes the tool's scope self-evident by naming Telegram and the specific things it validates, providing clear context for when it applies. It does not explicitly mention alternatives or state when not to use it, but the sibling tools are naturally distinguishable by service name.

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