transfer_gift

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

Adds the permission requirement, which annotations do not cover, so it goes beyond structured data. However, it does not disclose the key behavioral facts an agent needs: that ownership actually moves away from the current owner, whatever restrictions apply to the transferred unique gift, or why idempotentHint=true holds for a 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?

Two sentences, front-loaded with the action and followed by the prerequisite. No filler, though it is arguably too terse given the complexity of the operation.

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 four-parameter mutation with no output schema and zero schema coverage, the description covers purpose and one permission but leaves parameters and post-transfer effects undocumented. It is safe to select but not fully sufficient to invoke confidently.

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 names none of the four parameters. The most confusing one, the optional star_count, is left fully unexplained, as are the roles of business_connection_id and new_owner_chat_id.

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?

States a specific verb and resource: 'Transfer an owned unique gift to another user.' The word 'owned' plus 'unique' implicitly separates it from send_gift (new gift) and upgrade_gift, but no sibling is named, so differentiation is inferred rather than explicit.

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?

Gives one useful precondition – the can_transfer_and_upgrade_gifts business bot right – but says nothing about when to choose this over upgrade_gift, convert_gift_to_stars, or send_gift, and gives no failure or eligibility conditions.

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