telegram-send-reaction

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

Describes behaviors beyond annotations: supports multiple reactions, adding to existing, and removal by omitting emoji. Annotations already indicate mutation (readOnlyHint=false) and open world, so description adds useful 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?

Two concise sentences. Front-loaded with primary action. No redundant wording. Every sentence adds essential 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 main use cases and parameter behavior. Lacks mention of prerequisites (e.g., being a chat member) or error conditions, but acceptable for a simple tool with comprehensive schema and annotations.

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 descriptions already cover all 4 parameters. Description adds key behavior: omitting emoji removes all reactions, which is not explicit in the schema. This adds significant value.

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 the action (send emoji reaction), target (message), and supports multiple reactions, adding to existing, and removal. Distinct from sibling tools like telegram-send-paid-reaction and telegram-react-to-story.

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 clear context on usage (multiple reactions, add to existing, omit emoji to remove all). Does not explicitly exclude use cases or compare with alternatives, but a solid guideline is given.

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