hl_tx_list

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. The description adds almost nothing beyond that: it does not state pagination/ordering behavior, default page size, or whether fills and orders are merged or returned separately. For a list tool with four inputs, this leaves the agent under-informed about how results arrive.

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?

A single short sentence with the resource front-loaded and no filler. It is efficiently structured, though terseness here contributes to the specification gaps noted elsewhere rather than being purely a virtue.

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?

Four undocumented parameters, no output schema, and minimal annotations mean the description carries a large burden and does not meet it. An agent lacks guidance on pagination, dex scoping, and result shape before calling.

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 0%, so the description must compensate, but it only covers the required userAddress implicitly via "for a wallet". The dex, page, and limit parameters — including the pagination semantics that materially affect usage — receive no explanation anywhere.

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 ("Get HL transaction list (fills / orders) for a wallet"), which is more informative than a bare name. However, it does not distinguish itself from close siblings such as get_hl_trade_history, get_hl_open_orders, or get_hl_copy_trade_tx_list, which an agent could easily confuse it with. Purpose is inferable but not sharply scoped.

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?

There is no statement of when to use this tool versus the many alternatives, no prerequisites, and no exclusions. The agent must guess its place among get_hl_trade_history, get_hl_open_orders, and get_trade_history on its own.

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