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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond them: the node is operator-owned and lite, so historical block/transaction APIs are unavailable — an agent knows in advance that some related calls will fail.

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 resource and its fields, then cleanly segmented into when-to-use, when-not-to-use, and returns. No filler sentences; every clause carries information the agent can act on.

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, and the description compensates by naming the returned fields (height, solidity_height, solidity_lag_blocks, age_s, tx_in_tip_block, peer_count, client_version) plus what they mean for node health. Nothing needed to call this zero-arg tool correctly is 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?

Zero parameters, so per the rubric the baseline is 4; the input schema is empty with additionalProperties false and there is nothing parameter-level for the description to clarify.

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 a specific verb+resource ('TRON node state from our own java-tron full node') and enumerates the exact signals returned: tip height, solidity height and lag, peers, client version, tip-block tx count. This clearly separates it from siblings like tron_get_current_block or tron_get_block, which are about block data rather than node health.

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?

Explicit 'When to use' and 'Do not use' sections, with the exclusion justified ('this is a lite full node and those APIs are closed'). It does not name a concrete alternative tool for the historical case, so it stops short of the 5-level bar of routing the agent to a specific sibling.

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