gift_premium_subscription

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

Annotations already declare this a non-readonly, non-idempotent, open-world write, and the description adds nothing on top of that. Critically, it never mentions that star_count means real Telegram Stars are spent, that the operation is a payment-like transfer, or that it cannot be undone — exactly the behavioral context annotations cannot express.

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?

It is a single front-loaded sentence with no filler, but it is under-specified rather than concise. The version suffix '(v9.0)' consumes space without helping an agent decide or invoke correctly.

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 six-parameter, money-spending mutation with no output schema and near-zero schema documentation, one sentence is not enough. An agent has no way to know the cost model, the meaning of the required numeric fields, or what a successful gift returns.

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 only 17% (just user_id as 'User ID'), and the description supplies no parameter meaning at all. It does not explain month_count (duration of the gift), star_count (price in Stars), or the text/text_entities/text_parse_mode trio for an accompanying message.

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 names a specific verb and resource: 'Gift a Telegram Premium subscription'. That is far clearer than a tautology, but it never distinguishes this from the sibling send_gift, upgrade_gift, or transfer_gift, so an agent cannot tell which gifting path applies without opening schemas.

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?

There is no when-to-use guidance, no prerequisite conditions, and no explicit alternative named. The '(v9.0)' tag is a version marker, not usage guidance, leaving the agent to infer everything about applicability from the name alone.

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