prepare_tron_unfreeze

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

Annotations include destructiveHint=true and idempotentHint=true. Description adds context: returns a preview + opaque handle, requires send_transaction for execution, and outlines the 14-day cooldown and withdrawal step. No contradictions. Description provides workflow beyond annotations.

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?

Description is concise, with every sentence adding value. Front-loaded with purpose, followed by constraints and post-conditions. No fluff.

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 3-parameter tool with no output schema, the description provides sufficient context: explains the output (preview + handle), the required follow-up steps, and the constraint on amount. Could mention error cases beyond amount, but overall complete.

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 coverage is 100% and schema descriptions already detail each parameter. The description adds the prerequisite of querying get_tron_staking and the amount constraint, but does not significantly extend parameter semantics beyond what schema provides.

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?

Description clearly states it builds an unsigned TRON Stake 2.0 UnfreezeBalanceV2 transaction to begin the 14-day cooldown. Specifically identifies the action and resource, distinguishing it from freeze and withdraw siblings.

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?

Provides explicit when-to-use: to unfreeze previously frozen slice. Advises querying get_tron_staking first to check amount, and mentions the subsequent step of calling prepare_tron_withdraw_expire_unfreeze after 14 days. Also explains the need to forward via send_transaction for Ledger signing.

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