get_chain_parameters

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

With no annotations, the description carries the full burden and does well: it declares the tool read-only, free, keyless, and names the data source (a public node) plus the underlying node methods (getEnergyFee, getTransactionFee). It stops short of noting rate limits, failure modes, or freshness guarantees beyond "now".

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?

Front-loaded with the most decision-relevant qualifiers (read-only, free, no key) before the payload list. It is a single dense sentence, slightly overloaded by the parenthetical node method names, but every clause carries information.

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?

There is no output schema, so enumerating the returned fields (energy price, bandwidth price, free bandwidth, unstake delay) is genuinely necessary and is done here. Combined with the access and source disclosure, an agent has what it needs; only versioning/rate-limit caveats are missing.

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?

Only one optional parameter (network, with an enum) and schema description coverage is 100%, so the schema already fully documents it. The description adds nothing about mainnet vs nile behavior, making this a baseline 3.

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 gives a specific verb and resource (read the TRON fee parameters) and enumerates the exact contents: energy price, bandwidth price, free bandwidth per day, unstake delay. The word "now" implicitly separates it from get_energy_fee_history, but no sibling is named explicitly, so the differentiation is left to inference.

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?

It states the access conditions (read-only, free, no API key) and that values are current, which implies usage for a live fee snapshot rather than historical analysis. However, it never says when to pick this over get_energy_fee_history or get_prices, so routing is only implied.

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