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

Beyond the annotations (idempotentHint=true), the description discloses significant behavioral traits: configuration is in-memory and lost on restart/reconnect/redeploy, top-ups are signed locally with TRON_PRIVATE_KEY, and they are sent to a memo-routed Merx deposit address. This adds depth beyond the structured fields and is not contradictory.

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?

The description is three sentences: the first states the core purpose, the second details the session-only memory nature, and the third explains operational details and re-call necessity. Every sentence adds valuable context with no redundancy, and the most important info is 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?

Despite having no output schema, the description covers key aspects thoroughly: what the tool does, how it behaves (session-only, signing), where it sends funds, and how to maintain persistence. The annotations cover idempotency, and the schema covers parameters, so the description fills the remaining gaps effectively for a configuration tool.

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?

The input schema already covers all three parameters with descriptions (threshold_trx, deposit_amount_trx, max_daily_deposits), achieving 100% coverage. The description adds minimal additional meaning beyond rephrasing 'top-up when balance drops below a threshold.' Since schema coverage is high, a baseline of 3 is appropriate.

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?

The description clearly states the tool's function: 'Configure automatic top-up when balance drops below a threshold.' It uses a specific verb ('configure') and specific resource ('automatic top-up'), and distinguishes it from siblings like deposit_trx (manual deposit) and standing orders by emphasizing the session-scoped automatic condition.

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 description provides clear context on when to use it: it is session-scoped and must be re-called 'at the start of each session' for persistence. It does not explicitly point to alternatives or exclusions, but it clearly implies the temporal usage pattern. This meets 'clear context, no exclusions' rather than explicit alternative guidance.

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