setStickerEmojiList

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

With no annotations provided, the description carries the full behavioral burden. It states that this is a mutation ('Change'), identifies the ownership precondition, and discloses the return value ('Returns True on success'). This is solid behavior disclosure for a simple setter, though it does not mention potential failure conditions.

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 no filler. The core action is front-loaded, followed by the key constraint and return behavior. Every 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 low-complexity mutation with full schema coverage and no output schema, the description is complete: it states the operation, the target object, the ownership prerequisite, and the success return value. An agent has enough information to invoke 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?

Schema description coverage is 100%, so the baseline is 3; the schema already explains both parameters well. The description adds no additional parameter-level semantics beyond what the schema provides, so it does not exceed the baseline.

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 names a specific operation ('Change the list of emoji'), a clear resource ('regular or custom emoji sticker'), and the domain constraint ('sticker set created by the bot'). This clearly distinguishes it from sibling tools like setStickerKeywords or setStickerMaskPosition.

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 intended use case is stated directly: changing which emoji are assigned to a sticker. It also gives a key prerequisite (the sticker must belong to a bot-created set). It does not explicitly name alternatives or say when not to use it, but the context is clear enough for an agent to select it correctly.

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