get_copy_trade_tx_list

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

With no annotations, the description carries the full behavioral burden. It correctly implies a read operation ('List') and discloses the session-key auth requirement, which is genuinely useful, but says nothing about pagination, time-range scope, rate limits, or whether history is unbounded — significant gaps for a history-listing tool.

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 short sentences with zero waste; the core purpose is front-loaded and the auth prerequisite follows immediately. Nothing redundant.

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?

For a history-listing tool with no output schema, no annotations, and only two opaque parameters, the description should say more about what is returned (fields, ordering, time window, pagination). It is too thin to let an agent call it confidently against its many siblings.

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% (both userId and data are documented as control wallet address and AES-encrypted session key), so the baseline is 3. The description's 'Requires session-key auth' reinforces the purpose of the data parameter but adds no format or syntax detail beyond 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?

States a specific verb and resource ('List copy trade transaction history with PnL'), so an agent knows exactly what it retrieves. However, it does not distinguish itself from the near-identical sibling get_hl_copy_trade_tx_list, leaving the agent to guess which variant applies.

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 only guidance is the prerequisite 'Requires session-key auth.' There is no statement of when to use this tool versus get_hl_copy_trade_tx_list, get_copy_trade_list, or get_trade_history, and no exclusions or conditions.

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