TRON Energy/Bandwidth MCP Server

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

With no annotations provided, the description carries significant load by disclosing the sequence ('delegate energy before broadcasting'), payment mechanisms, and cost-estimation fallback. Missing explicit mention of blockchain submission permanence or error handling patterns.

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?

Three sentences efficiently structured: purpose declaration, input/process details, and authentication/cost behavior. No redundant text; every clause conveys distinct technical requirements (energy delegation, payment types, unauthenticated behavior).

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 coverage of the tool's unique value proposition (auto energy delegation) and operational modes. Given the complexity of blockchain transaction broadcasting and lack of output schema, it adequately covers the distinctive behavioral traits, though it could explicitly note the irreversible nature of broadcasting.

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 complete documentation of the nested txData structure. The description references 'signed transaction data' but does not add semantic details beyond the schema's description, which already covers the required fields and their purpose.

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 opens with specific verb 'Broadcast' + resource 'pre-signed TRON transaction' + distinguishing feature 'auto energy delegation', clearly defining the tool's scope. Mention of 'PowerSun' identifies the service provider for the energy delegation aspect, distinguishing it from the sibling 'broadcast_signed_permission_tx' which handles permission-specific transactions.

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 authentication guidance ('Works with API key... or x402 USDC payment') and clear fallback behavior ('Without authentication, returns cost estimate'). However, it lacks explicit comparison to sibling 'broadcast_signed_permission_tx' regarding when to use each broadcast method.

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