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

Beyond annotations, it discloses that the reaction is the bot's, that the recipient sees it and is notified, that only Telegram standard reaction emoji are accepted and the server merely relays Telegram's refusal, that the message must already be in the archive, and that business 1:1 chats are refused locally rather than failing obscurely. These are meaningful behavioral details for a destructive, open-world mutation.

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 content is dense and mostly earns its place, especially the emoji list and the exclusions. However, the description opens with an 'Also supports...' caveat before stating the main purpose, and the long final sentence about out-of-scope chats could be tightened.

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 four-parameter tool with an output schema absent but full schema coverage and annotations present, the description covers scope, emoji constraints, removal behavior, user confirmation, archive requirements, and the two excluded chat types. Nothing an agent needs in order to call it 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 would be 3, but the description adds real semantic value: the allowed emoji set is constrained in prose despite no enum in the schema, and omitting emoji is explained as removal. It also clarifies the chat and archive constraints on chat_id, though it does not explain the 'big' parameter.

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 and resource ('Put an emoji reaction on a message in a group the bot belongs to') and extends it to connected channels. It also explicitly distinguishes this tool from telegram_bot_dm_react and from business 1:1 chats, so an agent can select it without inspecting sibling schemas.

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?

It gives explicit when-to-use conditions (group the bot belongs to, connected channel posts after ownership verification) and explicit when-not-to-use cases (1:1 business chats, bot DM inbox, which routes to telegram_bot_dm_react). It also tells the agent to confirm the message and emoji with the user first, and explains that omitting emoji removes an existing reaction.

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