telegram-set-chat-reactions

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

The description explains the exact behavior for each type (all with allowCustom, some with emoji list, none disables). Annotations show readOnlyHint=false and openWorldHint=true, which align with the description. No contradictions.

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 description is two sentences, efficiently covering purpose and modes. No wasted words; front-loads the main action.

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?

Given no output schema, the description adequately covers the input and behavior. It does not specify return values, but for a set operation this is acceptable. The tool is well-situated among siblings.

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%, but the description adds meaningful context beyond schema definitions, such as the effect of allowCustom and the requirement for Premium users, and the max emoji limit. It also ties parameters to behavior.

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 clearly states 'Set which reactions are available in a chat' and explains the three modes (all, some, none) with specific details. This distinguishes it from sibling tools like telegram-get-reactions or telegram-set-default-reaction.

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 explicitly notes 'Requires admin', indicating when to use. It does not explicitly mention alternatives or when not to use, but the context is clear for a chat admin configuring reactions.

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