set_sticker_keywords

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

The description provides no behavioral details beyond the annotations, which already indicate a non-destructive, idempotent write. It does not disclose any potential side effects, permission requirements, or behavior when keywords are omitted.

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?

A single sentence with no filler, directly stating the action. It is front-loaded with the verb and resource.

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?

With no output schema and no parameter descriptions, the description offers minimal context. It does not explain what the tool returns, prerequisites, or the behavior when keywords are absent, leaving gaps for a mutation tool.

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 schema has 0% description coverage, so the description must compensate. It identifies that 'sticker' refers to the target sticker and 'keywords' to the new search keywords, but it does not explain formats, replacement vs. appending behavior, or the effect of omitting the optional keywords parameter.

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 changes search keywords for a sticker, using a specific verb and resource. It distinguishes from sibling tools like set_sticker_emoji_list and set_sticker_mask_position which modify other sticker attributes.

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 when you need to modify a sticker's search keywords, but it offers no explicit guidance on when to use it over alternatives or any contextual prerequisites. No alternatives or exclusions are mentioned.

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