telegram-set-emoji-status

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

The description adds behavioral context beyond annotations: requires Telegram Premium, explains how to clear status, and implies mutation (consistent with readOnlyHint=false). No contradictions. Lacks minor details like whether status is permanent by default or any limits, but still strong.

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 sentences: first establishes purpose and requirement, second gives usage pattern and sibling hint. No wasted words, front-loaded with critical info.

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 tool with 3 optional parameters and no output schema, the description covers requirement, setting/clearing behavior, and where to find IDs. Could mention if action is reversible or if it overwrites existing status, but 'omit both to clear' sufficiently implies that.

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 coverage is 100%, so baseline is 3. The description adds meaning: explains mutual exclusivity of documentId and collectibleId, and that omitting both clears status. Also clarifies untilUnix parameter. Does not repeat schema, adds usage context.

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 verb 'Set', the resource 'your profile emoji status', and explains what it is (custom animated emoji shown next to your name). It distinguishes from sibling tools like telegram-list-emoji-statuses by directing to use it for browsing IDs.

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?

Provides explicit when-to-use context: 'Requires Telegram Premium', and how to use: 'Pass documentId or collectibleId to set — omit both to clear the status.' It also directs to a sibling tool for browsing available IDs, offering clear guidance and alternatives.

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