get_transaction_log

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It correctly implies a read-only operation ('Get'), but it fails to disclose pagination behavior — the claim of a 'full ledger' sits awkwardly against the schema's count default of 100 and the need for continuation tokens — and says nothing about ordering, authentication, or response shape.

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 a single sentence with the core scope front-loaded ('full ledger of account transactions') followed by a clarifying enumeration. There is no filler, though the list of eight transaction types is somewhat long and partially duplicates the query enum already present in the schema.

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 6-parameter tool with no annotations and no output schema, the description is thin. It omits the return format, fails to explain that retrieving the full ledger requires pagination via the continuation parameter, and offers no guidance on when it should be preferred over the trade-specific sibling tools.

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%, so the schema already documents all six parameters, earning a baseline of 3. The description adds some value by enumerating ledger contents — including 'fees' and 'funding payments', which do not appear in the query enum — but this is largely redundant with the filter options already listed in 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?

The description uses a specific verb ('Get') and a specific resource ('full ledger of account transactions') and enumerates the transaction types in scope. The inclusion of trades, settlements, fees, funding payments, deposits, withdrawals, and transfers implicitly distinguishes it from trade-only siblings like get_user_trades and get_user_trades_by_instrument, though no sibling is named explicitly.

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 no guidance on when to use this tool versus the overlapping siblings get_user_trades and get_user_trades_by_instrument, which both concern the trade portion of the ledger. There are no conditions, exclusions, or alternative routing cues, leaving the agent to infer the appropriate selection from the name and scope alone.

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