setStickerMaskPosition

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

With no annotations, the description carries the behavioral burden. It discloses the ownership requirement and states that success returns True, which are useful. However, it does not describe side effects such as replacing an existing mask position or the fact that omitting mask_position removes it, though the schema does cover the latter.

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, information-dense sentence with no wasted words. It covers the operation, the key constraint, and the success return value in a compact way.

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 two-parameter tool with 100% schema coverage and no output schema, the description plus schema is largely sufficient. It adds the critical ownership prerequisite and success signal. It is slightly light on failure conditions and explicit removal behavior, but those are either implied or covered by the schema.

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 schema already documents both parameters thoroughly. The description adds no extra parameter-level meaning beyond restating that the tool changes mask position, which matches the baseline for full schema coverage.

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 uses a specific verb ('Change') with a precise resource ('mask position of a mask sticker'). This clearly distinguishes it from the sibling tool setStickerPositionInSet, which changes a sticker's order within a set, not its mask position.

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 gives a clear prerequisite: the sticker must belong to a sticker set created by the bot. It also implies the tool is only for mask stickers, which helps an agent decide whether this tool applies. It does not explicitly mention alternatives or exclusions, but the context is strong enough for correct selection.

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