telegram-get-my-boosts

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

The description states it is read-only, aligning with annotations. It adds behavioral context beyond annotations by listing the fields in each entry (slot index, peer, dates, cooldown), which helps the agent understand the output structure. No contradictions with annotations.

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 three sentences with no wasted words. It front-loads the purpose and efficiently conveys all necessary information.

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 no output schema, the description adequately explains the return fields and differentiates between Premium and non-Premium users. It could mention authentication requirements, but overall it provides sufficient context for a read-only tool with no parameters.

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?

There are zero parameters, so the description does not need to add parameter details. According to guidelines, baseline is 4 when no parameters exist.

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 it lists the user's premium boost slots, with specific detail about the internal API method and distinguishes from sibling tools that deal with boosts in other contexts (e.g., telegram-get-boosts-list, telegram-get-boosts-status).

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 provides context on Premium vs non-Premium users and slot count, which guides when the tool is applicable. However, it does not explicitly state when not to use it or differentiate from sibling tools like telegram-get-boosts-status, leaving some ambiguity.

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