transfer_gift

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

Annotations already convey non-read-only, non-destructive, and idempotent behavior. The description adds no extra context about side effects, ownership changes, or requirements, such as the need for a business connection. It essentially restates the tool name.

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 front-loaded, which is good for conciseness. However, the parenthetical '(v9.0)' is unnecessary fluff and does not enhance understanding, slightly reducing the score.

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 mutation tool with three required parameters and no output schema. The description is too sparse to be complete, especially given the many gift-related sibling tools. It fails to explain the role of business_connection_id or the implications of transferring a gift.

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?

With 0% schema description coverage, the description must compensate, but it does not mention any of the three required parameters (business_connection_id, owned_gift_id, new_owner_chat_id). No meaning is added beyond the parameter names themselves.

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 specific action 'Transfer a gift' and the recipient 'to another user', effectively distinguishing it from siblings like send_gift. The version marker 'v9.0' is minor but does not confuse the core purpose.

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 such as send_gift or convert_gift_to_stars. The description lacks any indication of prerequisites, exclusions, or typical use cases.

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