TRON infrastructure for AI agents.

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

Without annotations, description carries disclosure burden. Adds 'No auth required' (access constraint) and 'check on-chain status' (indicates blockchain query), though could clarify what specific on-chain status means (exists, activated, etc.).

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 sentences with zero redundant content; first establishes purpose, second provides auth context. Efficiently structured with critical information front-loaded.

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?

For a single-parameter validation tool without output schema, description adequately covers primary function and operational constraints. Mention of 'on-chain status' hints at return value meaning.

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?

Schema has 100% description coverage for the single 'address' parameter. Description does not add semantic details, syntax examples, or format specifications beyond the schema baseline.

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?

Validate a TRON address format' provides specific verb and resource, while 'check on-chain status' distinguishes from simple format validation or conversion tools like convert_address. The scope is clearly defined against sibling tools.

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?

States 'No auth required' indicating it can be used without credentials, but lacks explicit comparison to siblings like check_address_resources or convert_address. No 'when-not-to-use' or alternative guidance is provided.

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