get_custom_emoji_stickers

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety. The description adds minimal behavioral context beyond stating it's a read operation, which is consistent with annotations. No contradiction, but no extra details like return format or potential errors.

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 a single, concise sentence that front-loads the action and resource. Every word contributes meaning, with no filler or redundancy.

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 getter with one parameter and strong annotations, the description is adequate. It lacks explicit return value information, but given the straightforward nature of the tool and the readOnly/idempotent annotations, the context is sufficiently complete for an agent to use it correctly.

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 description's 'by their identifiers' maps directly to the single parameter custom_emoji_ids, clarifying its purpose. Since the schema provides no description for the parameter, this contextual hint adds meaning, though it doesn't elaborate on the format or expected structure of the IDs.

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 operation ('Get information') and the specific resource ('custom emoji stickers'), with the method ('by their identifiers'). This distinguishes it from sibling tools like get_sticker_set or get_forum_topic_icon_stickers, making the purpose unambiguous.

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 implies usage context: call this when you have identifiers for custom emoji stickers and need their information. It doesn't explicitly exclude alternatives, but the resource is specific enough that no confusion arises with sibling tools.

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