convert_gift_to_stars

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

The description adds no behavioral context beyond what annotations and the tool name convey. It does not mention that the gift will be consumed, that Stars are credited to the business account, or any side effects or auth requirements. The openWorldHint suggests external effects, but no details are given.

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 very short and to the point, but the inclusion of '(v9.0)' adds noise without value, preventing a perfect score. Otherwise, the single sentence is efficient.

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?

This is a financial operation (converting a gift to Stars) with no output schema, yet the description provides no information about prerequisites, success behavior, or potential errors. It is not complete enough for an agent to use safely without additional clarification.

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%, and the description does not explain either parameter. The agent must infer the meaning of business_connection_id and owned_gift_id solely from their names, which is insufficient for reliable tool invocation.

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 action ('Convert a gift') and the result ('to Telegram Stars'), with a specific verb and resource. It distinguishes from sibling tools like upgrade_gift and transfer_gift by focusing on conversion to Stars.

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, nor any prerequisites or exclusions. The context signals show many related gift tools, and the description does not help select between them.

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