TRON infrastructure for AI agents.

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

With no annotations provided, the description must carry the full behavioral burden. It discloses the session-scoped nature ('Session-only'), which is essential. However, it omits mutation details such as whether this creates immediate transactions, overwrites previous auto-deposit settings, or what happens on trigger failures.

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 redundancy. Front-loaded action ('Configure automatic top-up') followed by constraint ('Session-only'). Minor ambiguity in whether 'Session-only' refers to the configuration duration or deposit timing prevents a 5.

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 simple 3-parameter schema and lack of annotations/output schema, the description covers the essential purpose and session constraint. However, it omits expected return values, side effects (e.g., interaction with existing monitors), and disable/cancellation procedures, leaving moderate gaps.

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 description coverage is 100% (threshold_trx, deposit_amount_trx, max_daily_deposits fully documented). The description mentions 'threshold' generally but does not add semantic value beyond the schema—such as explaining why amounts are strings not numbers, or the relationship between threshold and deposit amount.

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?

Specific verb 'Configure' and clear resource 'automatic top-up' identify the tool's function. The phrase 'when balance drops below a threshold' defines the trigger condition, and 'Session-only' distinguishes this from persistent automation siblings like create_standing_order. However, it does not explicitly contrast with manual deposit_trx.

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?

The 'Session-only' constraint provides critical usage context (configuration expires with session). However, it lacks explicit guidance on when to choose this over manual deposits (deposit_trx) or persistent standing orders, and does not state prerequisites like minimum balance requirements.

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