TRON Energy/Bandwidth MCP Server

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

Discloses the API key authentication requirement, which compensates somewhat for missing annotations. However, fails to explicitly state that this is a read-only operation (critical for a financial tool), doesn't mention rate limits, idempotency, or what specific 'deposit information' entails beyond the balance.

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 efficient sentences. First sentence declares the core function (balance retrieval), second states the auth requirement. No redundancy or filler content.

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?

Describes the conceptual return values (balance and deposit info) despite lacking an output schema, which is helpful. However, given zero annotations and no output schema, the description should provide more behavioral context (read-only assurance, response structure) for a financial data tool.

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?

Zero parameters present per input schema, triggering the baseline score of 4. The description wisely avoids inventing parameters that don't exist in 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?

States specific action (Get) and resource (current TRX balance and deposit information). TRX specificity helps identify this as a Tron blockchain balance tool. Minor ambiguity exists with sibling 'get_deposit_info' since both mention deposits, but the combination of balance+deposit info provides differentiation.

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?

Identifies the authentication prerequisite ('Requires API key authentication'), which is crucial given no annotations. However, lacks guidance on when to use this versus siblings like 'get_deposit_info' (which also handles deposits) or 'get_available_resources', and doesn't indicate if this is for the user's own account or can query others.

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