send_group_sticker

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

No annotations exist, so description carries full burden. It explains that sticker is rendered as a distinct message type, not file attachment, and that invalid pack/sticker returns error. Could additionally mention lack of side effects or permissions, but the existing disclosure is strong.

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?

Description is adequately concise with front-loaded purpose. Every sentence adds value, though it could be slightly tightened. No extraneous 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?

For a tool with 3 required parameters, no annotations, and no output schema, the description covers purpose, usage, parameter semantics, prerequisites, and alternatives. An agent can correctly select and invoke the tool without gaps.

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 cover 100% of parameters, and the description adds value by explaining that pack_id is a hex string, sticker_id is 0-based, and both must match an installed pack. Also explains how to obtain them via list_sticker_packs, going beyond 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?

The description clearly states it sends a sticker to a Signal group, distinguishes it from sending images (use send_group_attachment instead) and from direct messages (use send_sticker). It uses specific verb+resource and identifies the unique action.

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 explicit when-to-use (expressive image reaction in group), when-not-to-use (for regular images or DMs), and prerequisites (list_groups, list_sticker_packs, add_sticker_pack if needed). Directly names alternative tools.

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