prepare_tron_trc20_approve

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

The description adds significant behavioral context beyond annotations: refusal to default decimals with a clear safety rationale, and return value specification. Annotations indicate destructiveHint=true, and the description aligns with that by warning about off-by-power-of-ten. No contradiction.

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 well-structured with front-loaded purpose, then usage, constraints, and safety rationale. Every sentence adds value without verbosity.

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 complex tool with 6 parameters and no output schema, the description explains the return value and all important constraints. It covers purpose, usage, special cases, and safety warnings, making it complete for agent invocation.

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%, so baseline is 3. The description adds meaningful context: clarifies spender typical use, amount as human decimal string with 'max' unsupported, and decimals refusal reason. Provides extra clarity beyond 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 clearly states the verb 'Build an unsigned TRC-20 approve tx' and the specific resource. It distinguishes itself from sibling prepare_* tools by specifying it's for TRC-20 approve and for use before prepare_tron_lifi_swap.

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 explicitly states the primary use case (authorize LiFi Diamond before prepare_tron_lifi_swap), what not to do (no unbounded approvals), and when it's required (pass decimals for non-canonical tokens). It provides clear guidance on when to use vs. avoid.

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