send_sticker

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

Without annotations, description carries burden. Notes immediate sending and single send per call, but lacks details on side effects (e.g., cost, rate limits, error handling, notifications). Moderate transparency.

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 with front-loaded action verb. Every word adds value; no redundancy. Excellent structure.

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 basic operation and target contexts, but missing output/response description and error scenarios. For a send tool with no output schema, more detail on success/failure would improve completeness.

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 100%, but description adds value by explaining naming convention (STKID, STKPKGID) and source of valid IDs. Version parameter gets no extra context beyond schema, so not perfect.

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 the tool sends a LINE sticker, specifies identification via stickerId + packageId, and distinguishes from other send tools by focusing on stickers.

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 when-to-use context (owned stickers, 1:1/group/room) and prerequisites (get IDs from search_stickers/list_stickers). Could explicitly mention when not to use (e.g., if sticker not owned) but context is sufficient.

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