transfer_business_account_stars

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the agent knows it's a non-destructive write. The description adds the action semantics but doesn't disclose additional behavioral details such as failure modes or effects on balances beyond the transfer.

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?

One concise sentence, no redundancy, front-loaded.

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 the simple two-parameter tool with good annotations, the description is adequate but lacks context about prerequisites (e.g., how to obtain business_connection_id) and expected response. It is not fully complete but acceptable for a simple transfer operation.

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 schema provides no descriptions (0% coverage), and the description does not explain the parameters. While the names business_connection_id and star_count are somewhat self-explanatory, the description does not clarify where to obtain the connection ID or any constraints beyond the schema.

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 uses a specific verb 'transfer' and clearly identifies the resource (Telegram Stars), source (business account), and destination (bot), distinguishing it from sibling tools like get_business_account_star_balance or refund_star_payment.

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 implies usage (when you need to move stars from a business account to the bot) but does not explicitly mention when to use it versus alternatives, nor does it state prerequisites like needing an active business connection.

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