TRON infrastructure for AI agents.

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

With no annotations, the description carries full behavioral burden. It discloses the authentication requirement (MERX_API_KEY) but omits other critical behavioral traits such as pagination behavior, default/maximum result limits, data freshness, or whether the operation is read-only and safe.

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: first states purpose, second states auth requirement. 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?

Given the lack of output schema and annotations, the description covers the minimum (purpose + auth) but leaves gaps. For a transaction history tool likely returning variable-length datasets, omitting pagination details, result limits, or output payload expectations makes this incomplete.

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?

Input schema has 100% description coverage ('Time period to query. Default: 30D.'), so the baseline score is 3. The description adds no parameter-specific semantics (e.g., it does not mention the 'period' parameter, valid formats, or the default), but it does not need to compensate given complete schema documentation.

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?

Clear verb+resource ('Get...transaction history') and scope ('Merx account'). Deducted one point because it fails to distinguish from sibling 'search_transaction_history'—it is unclear when to use this time-bounded list versus the search variant.

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?

Mentions the prerequisite 'Requires MERX_API_KEY', which is relevant to usage. However, provides no guidance on when to use this tool versus 'search_transaction_history' or 'get_transaction' (singular), or any exclusion criteria.

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