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 the full burden by disclosing on-chain processing, potential delays (few minutes), and minimum amount constraints. Could improve by mentioning irreversibility or auth requirements.

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 well-structured sentences with zero waste: action definition, business constraint, and processing behavior are all front-loaded and essential. Slightly less concise than the two-sentence ideal but efficient.

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 single-parameter financial tool but missing critical safety context given no annotations: irreversibility, authorization requirements, and failure modes are not disclosed.

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 the baseline score applies. The description repeats the minimum withdrawal constraint already documented in the schema parameter description but adds no additional semantic guidance beyond the 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?

Clearly states the action (withdraw), resource (TRX from account balance), and destination (wallet), but does not explicitly differentiate from sibling tools like get_earnings or execute_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?

Provides critical constraint (100 TRX minimum) but offers no guidance on when to use this tool versus alternatives like get_earnings or execute_swap, nor prerequisites for execution.

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