set_default_telegram_account

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

With no annotations, the description carries the full behavioral burden. It does disclose the key effect (sets the default account for all telegram_* calls), but says nothing about persistence, whether the target account must already be connected, failure behavior for an unknown account, or how the change is reverted. Adequate but with real gaps for a state-mutating tool.

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 sentence with zero filler, front-loading the action and following with the precise scope of effect. Nothing could be trimmed without losing information.

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?

No output schema and no annotations, so the description must stand alone. It covers purpose and effect, but leaves the most operationally important question unanswered: how the agent identifies which Telegram account becomes the default when the tool accepts no parameters.

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 and the schema declares an empty object, so there is no parameter semantics to clarify; the description adds the only semantic it can, namely that the setting acts as a fallback when no `account` argument is supplied. The selection mechanism itself is unexplained, but with no schema fields the baseline of 4 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?

States a specific verb ('Choose'/'set default') and resource (Telegram account) plus the exact scope of effect: the telegram_* tools and the 'no `account` given' fallback condition. This distinguishes it cleanly from siblings like telegram_list_accounts and from set_default_whatsapp_account/set_default_m365_account.

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 a clear usage condition — it controls what telegram_* tools do when no `account` argument is passed — which is exactly the when-to-use context an agent needs. It does not mention exclusions or point at the parallel set_default_whatsapp_account tool, so the routing guidance is good but not fully explicit.

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