telegram-set-chat-reactions

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

Discloses mutation (set) and admin requirement. Explains three reaction modes and allowCustom option. Adds value beyond annotations (readOnlyHint=false, openWorldHint=true) by detailing behavior for each type.

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?

Two sentences, first states purpose, second elaborates on modes and admin requirement. No filler words, efficiently conveys key 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?

Covers essential elements: what it does, modes, admin requirement. Lacks mention of return value or side effects, but for a simple configuration tool this is acceptable.

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% with descriptions for each property. Description adds a compact explanation of the three reaction types and the allowCustom flag, making it easier to understand the choices without parsing the full schema.

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?

Description clearly states verb 'Set' and resource 'reactions' with scope 'in a chat'. Differentiates from siblings like telegram-get-reactions and telegram-send-reaction by focusing on configuration, not retrieval or sending.

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?

Provides admin requirement but no explicit guidance on when to use this tool versus alternatives like get-reactions to check current state. Context is implied but not explicitly stated when not to use.

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