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

Annotations already flag destructive/openWorld/non-idempotent, but the description adds traits those hints cannot convey: the group-vs-private identity switch ('In a group there is no business connection, so it is sent as the bot'), the zero-cost/no-size-limit forwarding behavior, and the live-vs-imported file-id limitation. This is genuinely additive context.

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?

Front-loads the action and the irreversibility warning, then uses two tight bullets to separate the source paths. Every sentence carries information; the length is justified by the tool's multiple modes and eight parameters.

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 exists, so the description must carry behavioral burden — and it does: confirmation requirement, source-selection rules, group identity caveat, and forwarding limitations. Nothing an agent needs to invoke this correctly 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 coverage is 100%, so the baseline is 3; the description rises above it by explaining the mutually exclusive url vs from_chat_id+from_message_id semantics and their cost/limit implications. The remaining parameters (caption, as_document, thread/reply ids) get no extra meaning beyond the schema, so it is not a full 5.

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 (send) plus the full resource set (photo, document, video, audio, voice message) and the target (real person or group from the user's Telegram). This distinguishes it cleanly from telegram_send_message (text) and telegram_get_file/get_photo without opening any schema.

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?

Gives explicit when-to-use guidance for the two source paths ('Give exactly one source', with the forwarding path vs the url path and their trade-offs), and a clear exclusion ('Works only for messages the collector saw live; imported history has no file id'). It does not, however, route the agent against sibling send tools, so it stops short of full 5-level guidance.

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