Change the mask position of a Telegram mask sticker by specifying the sticker and new position, enabling correct mask placement for custom sticker effects.
Change the mask position of a mask sticker.
| Name | Required | Description | Default |
|---|---|---|---|
| sticker | Yes | ||
| mask_position | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond what the annotations already provide. Annotations indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, and the description merely says 'Change' without elaborating on effects, reversibility, or required permissions.
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, succinct sentence with no unnecessary words. It is well-structured and front-loaded, but it could be more informative without becoming verbose.
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?
Given the two-parameter tool with no output schema and no parameter descriptions, the description is too minimal to be complete. It doesn't specify valid values for mask_position or how it should be formatted, leaving the agent uncertain about how to invoke the tool 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 0% for both parameters. The description does not explain what 'mask_position' accepts (e.g., coordinates, string, percentage) or how 'sticker' should be specified. It adds no value to the bare schema.
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 a specific action ('Change the mask position') on a specific resource ('mask sticker'). It distinguishes itself from sibling tools like set_sticker_position_in_set because it refers to the mask position, not the position within a sticker set.
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?
No guidance is provided on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or when a different sticker-modification tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.