unwrap_trx

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

Beyond annotations (destructiveHint: true), description adds important details: 'you burn your own WTRX', contract method 'withdraw(uint256)', and 1:1 rate. No contradiction with 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?

Two sentences, front-loaded with core action (unwrapping, rate). Second sentence covers key details (no approval, pre-checks, reversal). No wasted words.

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?

Adequate for a simple unwrap with clear pre-conditions, but lacks mention of return value (receipt?) or post-unwrap state. Since no output schema, description could be more 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% with clear descriptions for both parameters (amount, network). Description adds no new parameter semantics beyond what schema provides, meeting baseline but not exceeding.

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?

Clearly states it unwraps WTRX to native TRX at a 1:1 rate via the WTRX contract. The verb 'unwrap' is specific to the resource 'WTRX' and contrasts with 'wrap_trx' listed among 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 context: no approval needed, pre-checks (sufficient WTRX balance, TRX for gas), and relationship to wrap_trx. It clearly guides when to use this tool, though it could mention when alternatives are preferable.

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