TRON Energy/Bandwidth MCP Server

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

No annotations provided, so description carries full burden. Discloses critical behavioral traits: automatic energy delegation occurs 'before broadcast', and supports two payment modes (API key balance deduction or x402 USDC). Lacks explicit mention of destructive/mutating nature or return value format, but covers major operational side effects.

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?

Four efficient sentences with zero waste: purpose declaration, workflow prerequisites, energy delegation timing, and payment methods. Front-loaded with main action, followed by procedural and technical constraints.

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?

Comprehensive for complex blockchain operation despite missing output schema. Covers payment authorization, energy side effects, and transaction prerequisites. Would benefit from describing success/failure outputs or confirmation behavior, but sufficient 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%, establishing baseline 3. Description adds workflow context beyond schema: emphasizes txData must be pre-signed and sourced from get_swap_quote, clarifying the parameter's provenance and required state before submission.

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 specific action (execute) with resource (pre-signed swap transaction) and key feature (automatic energy delegation). Clearly distinguishes from generic broadcast_transaction sibling by specifying swap-specific functionality and energy delegation.

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 workflow: 'Get the unsigned TX from get_swap_quote, sign it, and submit here.' Names prerequisite tool (get_swap_quote) and establishes clear sequence. Also documents payment alternatives (API key vs x402 USDC), helping agent select appropriate auth method.

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