telegram_send_reaction

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds a real operational prerequisite not present in structured fields — the bot must already be a member of the chat — which materially affects whether the call will succeed. It omits whether a reaction replaces a prior one or rate limits, keeping it from a 5.

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 short sentences with zero filler; the core action leads and the precondition follows. Every clause earns its place.

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, but annotations plus the full-coverage schema plus the membership precondition give an agent enough to call correctly. Minor gaps remain around failure modes and whether reactions overwrite, which a single clause could close.

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 all three parameters are already documented, which sets the baseline at 3. The emoji examples add flavor but don't constrain the allowed emoji set, and the description adds nothing for chat_id/message_id beyond the 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?

States a specific verb and resource: 'Set an emoji reaction on a message.' This clearly distinguishes it from the send_message/send_photo/send_file siblings, which create messages rather than react to existing ones. It stops short of naming siblings explicitly, but the distinction is obvious.

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 emoji examples (👀 working, ✅ done, ❌ failed) imply a progress-reporting use case and the membership precondition is stated, but there is no explicit when-to-use vs. when-not guidance nor a pointer to any alternative tool. Usage is implied rather than directed.

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