telegram_send_message

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

No annotations are provided, so the description carries the full burden. It discloses only that sending happens from "your own account," which hints at a user-auth context, but says nothing about required account state, failure modes, rate limits, or what happens when multiple accounts exist.

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 wasted words, and the sender context precedes the destination. It is efficient, though it is arguably too terse for a mutation tool with unresolved targeting.

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 an empty input schema, the description should explain prerequisites (connection/account selection) and what confirmation the caller gets. Neither is covered, leaving the agent unable to know whether the send succeeded or which account/chat was used.

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 input schema is empty (0 params), so the usual baseline is 4, but the operation inherently requires a target chat and message body that appear nowhere in the schema, and the phrase "to one chat" points at target ambiguity the description never resolves. The description therefore adds no real parameter semantics and leaves a meaningful gap.

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 a specific verb and resource ("Sends a Telegram message") and scopes it ("from your own account to one chat"), which is enough to distinguish it from the platform siblings like whatsapp_send_message or teams_send_message. It does not, however, explicitly differentiate itself from telegram_connect/telegram_read_messages or state when this is the right send path.

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 guidance, no prerequisite note that an account must first be connected via telegram_connect, and no mention of how the default account (set_default_telegram_account) interacts with sending. The agent must infer all of this from the tool name.

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