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 and discloses significant behavioral traits: it explains that the tool creates both a pool and auto-selling configuration, clarifies that the platform will subsequently vote/delegate on the user's behalf, and states the API key authentication requirement. Minor gap: it doesn't mention return value structure, idempotency, or error conditions.

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 sentences with zero waste: sentence 1 defines the action, sentence 2 describes created artifacts, sentence 3 lists critical post-requisites with specific permission names, and sentence 4 gives verification instructions plus auth requirements. Information is front-loaded and logically sequenced.

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?

Given the medium-high complexity (blockchain permissions, delegation, voting), 100% schema coverage, and lack of output schema/annotations, the description adequately covers the registration workflow and permission model. Minor deduction for not describing the return value (e.g., pool ID, confirmation status) or whether registration is idempotent.

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?

While the schema has 100% coverage (baseline 3), the description adds valuable business context by framing the booleans (sellEnergy, sellBandwidth, autoVote) within the 'selling pool' concept and explaining that auto-voting is for 'best Super Representative' rewards. It could be elevated to 5 by explaining parameter interactions (e.g., what happens if both selling options are false).

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 a specific verb (Register), resource (TRON address), and scope (energy/bandwidth selling pool on PowerSun). It clearly distinguishes this as a creation/setup tool rather than configuration or querying tools found in the sibling list.

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?

Excellent workflow guidance: it explicitly states the post-requisite (grant active permissions), lists the specific permission types needed (DelegateResource, UnDelegateResource, VoteWitness), references the exact sibling tool for verification (check_pool_permissions), and notes the API key requirement. This creates a clear when-to-use and what-to-do-next narrative.

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