getCustomEmojiStickers

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

No annotations are provided, so the description carries the full disclosure burden. It reveals the output is an 'Array of Sticker objects' and implies a read-only operation via 'Get information', but it does not mention error behavior, empty results, ordering, authentication needs, or rate limits. For a simple read tool this is adequate but not comprehensive.

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?

The description is two short, front-loaded sentences with no filler. The first sentence states the action and resource, the second provides the return type, and each sentence 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?

For a single-parameter read operation with a fully described schema, the description covers the essential facts: what is fetched and what is returned. The explicit return type is valuable given the absence of an output schema. It omits error handling and permission context, but the simplicity of the operation makes those gaps non-critical.

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 description coverage is 100%, so the input schema already documents the identifier list and the 200-item limit. The description only restates that values are identifiers, adding no format or constraint details beyond the schema, hence the baseline score.

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 states a specific verb ('Get'), a specific resource ('custom emoji stickers'), the method of lookup ('by their identifiers'), and the return type ('Array of Sticker objects'). This clearly distinguishes it from sibling tools like getStickerSet or getForumTopicIconStickers.

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?

There is no explicit guidance on when to choose this tool over alternatives, nor any exclusions. The phrase 'by their identifiers' implies the condition for use, but it does not compare against getStickerSet or other sticker-related tools, leaving the agent to infer usage context from the tool name alone.

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