TRON Energy/Bandwidth MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it lists the logical content returned, it omits operational characteristics such as whether the operation is read-only, idempotent, requires authentication, or has rate limiting/cost implications. It doesn't contradict the absence of annotations, but fails to fill the gap.

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?

The description consists of two efficient sentences. The first defines the scope and contents, the second provides usage context. There is no redundant or wasted language; every clause earns its place.

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 absence of an output schema, the description adequately compensates by enumerating the specific data categories returned (prices, availability, etc.). For a parameter-less aggregator tool, this level of detail is sufficient, though structural details about the response format would strengthen it further.

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?

The input schema has zero parameters, which establishes a baseline score of 4 according to the evaluation rubric. With no parameters to describe, the description appropriately focuses on the tool's output rather than inputs.

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 clearly states it provides a comprehensive market overview and enumerates specific data components returned (prices, availability, durations, constraints, transaction types). However, it does not explicitly differentiate this aggregate view from sibling tools like 'get_prices' or 'get_available_resources' which appear to return subsets of this data.

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?

The description includes one usage scenario ('Useful for agents to understand what they can purchase'), providing implied context for when to use it. However, it lacks explicit guidance on when NOT to use it (e.g., when specific getters are preferred) or prerequisites for invocation.

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