convertGiftToStars

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states the permission requirement, the conversion action, and the return value ('Returns True on success'). However, it does not describe failure behavior, side effects, or the condition of the original gift after conversion, which would be useful for a mutation-like operation.

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 two concise sentences. The key action and permission are front-loaded, and the return value is stated clearly with no filler or repetition of schema details.

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 two-parameter tool with a fully described schema, the description provides the essential context: the action, the permission prerequisite, and the success return. It does not specify error conditions or whether the gift is consumed, but given schema completeness and no nested objects, the description is sufficiently complete for correct invocation in most cases.

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?

The input schema already covers 100% of parameters with descriptions, so the baseline is 3. The description does not add parameter-level meaning beyond the schema, but it confirms the overall operation and the required permission, which indirectly clarifies why both parameters are needed.

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 verb ('Converts') and resource ('regular gift to Telegram Stars'), and mentions a required permission ('can_convert_gifts_to_stars business bot right'). This distinguishes it from sibling gift tools like upgradeGift, transferGift, and getBusinessAccountGifts.

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 names a required permission, which indirectly tells an agent the tool can only be used when that right is present. It does not explicitly mention alternatives or when not to use it, but the permission requirement and the verb 'convert' give clear context compared to siblings.

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