prepare_tron_freeze

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

Annotations indicate destructiveHint=true and idempotentHint=true; description adds that it builds an unsigned transaction, requires send_transaction, and that freezing alone does not accrue rewards. No contradictions. Describes return type (preview + opaque handle) but lacks details on the return structure, which is acceptable given no output schema.

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 well-structured: starts with core purpose, then caveats, alternatives, and integration steps. Every sentence is informative and non-redundant. Efficient for an AI agent.

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?

Covers the main action, rewards context, lock-up period, and related tools. Lacks specifics on the preview format and error cases, but overall sufficient for a complex staking tool. No output schema, so description could be more detailed, but it remains helpful.

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?

All three parameters are documented in the schema (100% coverage). Description adds value by clarifying that amount is a human-readable decimal converted to SUN internally, resource enum meanings, and the from address prefix T. Extra context beyond schema descriptions.

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 tool builds an unsigned TRON Stake 2.0 FreezeBalanceV2 transaction, specifying the action (freeze), resource (TRX), and outcomes (earn bandwidth/energy, gain voting power). It distinguishes from siblings like prepare_tron_vote and prepare_tron_unfreeze.

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?

Explicitly states when to use (to earn bandwidth/energy and voting power), what not to expect (no rewards without voting), and references related tools (list_tron_witnesses, prepare_tron_vote, prepare_tron_unfreeze, prepare_tron_withdraw_expire_unfreeze). Also mentions the 14-day cooldown for unlocking.

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