get_sticker

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

No annotations are provided, so the description carries the full burden. It implicitly indicates a read-only operation by stating 'retrieve'. It does not mention side effects, permissions, or error conditions, but for a simple retrieval tool, the disclosure is adequate.

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 the purpose and output format, second provides usage guidance. No unnecessary words, all information is relevant and front-loaded.

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 simple retrieval tool with two parameters and no output schema, the description is complete. It explains what the tool does, how to get the required parameters, and the format of the result (base64). No 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?

The input schema already fully describes both parameters (pack_id and sticker_id) with types and explanations. The description adds a hint to use list_sticker_packs to find values, which is helpful but does not add meaning beyond the schema. With 100% schema coverage, baseline score is 3.

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 retrieves a single sticker image as base64. It specifies the action (retrieve), resource (sticker image), and output format (base64). This distinguishes it from sibling tools like send_sticker or list_sticker_packs.

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 description instructs the agent to use list_sticker_packs to find the required IDs, providing a clear prerequisite step. However, it does not explicitly state when to use this tool versus alternatives like send_sticker or send_group_sticker, though the context makes it obvious.

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