TRON infrastructure for AI agents.

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

Since no annotations are provided, the description carries full behavioral burden. It successfully discloses 'No auth required' but fails to confirm read-only safety, describe what specific block data is returned, or mention rate limits/idempotency for this blockchain operation.

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 waste. Main action 'Get TRON block info by number' is front-loaded, followed by parameter optionality and auth requirements. Every word 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?

Adequate for a simple single-parameter tool without output schema. Covers core function, optional parameter behavior, and auth requirements. Could be improved by briefly characterizing what 'block info' includes or confirming the read-only nature.

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 coverage is 100% (parameter fully described as 'Block number. Omit for latest'), establishing baseline 3. Description adds domain context 'TRON' but largely restates the optional parameter behavior already documented 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?

Description uses specific verb 'Get' with resource 'TRON block info' and parameter context 'by number', clearly distinguishing it from sibling tools like get_transaction, get_account_info, or get_balance which handle transactions, accounts, and balances respectively.

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?

Provides parameter usage guidance '(or latest if omitted)' and prerequisite 'No auth required', but lacks explicit guidance on when to use this tool vs. alternatives like get_transaction or get_transaction_history.

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