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

Annotations already declare destructive/not-idempotent/not-readOnly, so safety is partly covered. The description adds genuinely useful behavioral context beyond that: the required credentials (MERX_API_KEY + TRON_PRIVATE_KEY) and the critical caveat that broadcast acceptance does not mean the deposit is credited.

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?

Three short sentences, zero filler, and the core action and destination are front-loaded before the caveats. Every sentence carries distinct information.

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?

No output schema exists, and the description covers the key post-condition risk (accepted broadcast ≠ credited deposit) plus the credential prerequisite. It leaves minor gaps around confirmation timing and whether the personal deposit address is auto-resolved, but is largely complete for a single-parameter deposit 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?

Only one parameter (amount_trx) with 100% schema description coverage, so the schema already documents it. The description adds no format, precision, minimum, or unit detail beyond what the schema provides, making this baseline territory.

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?

States a specific verb (send) and resource (plain TRX transfer) plus the exact destination (personal Merx deposit address). This implies a distinction from the sibling transfer_trx (arbitrary recipient), but never names that sibling, so the differentiation is left to inference.

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?

It notes 'No memo is required' and that broadcast acceptance does not equal credit, which implies usage context. However, there is no explicit statement of when to use this versus transfer_trx or withdraw, nor any prerequisite ordering beyond the key requirement.

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