fetch_transaction_list

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions 'superficial information,' hinting at limited detail but does not state read-only nature, pagination behavior, or any side effects. For a fetch tool, disclosure of idempotency or rate limits would be beneficial.

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, concise sentence that quickly conveys the tool's purpose. However, it could be structured with bullet points or separate sentences for clarity, especially given the lack of parameter explanations.

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?

Given no annotations, no output schema, and three parameters with zero schema descriptions, the description is severely incomplete. It offers no information on pagination, time filtering, returned data structure, or how this tool fits into the broader workflow among 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?

With 0% schema description coverage, the description must elucidate parameter meanings. It does not mention cursor, time, or limit, leaving their purposes unclear. Parameters like 'cursor' and 'limit' typically relate to pagination, but the description provides no context.

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 fetches 'superficial information about movements to and from your account,' indicating it retrieves transaction-like data. The verb 'fetch' and resource 'transaction list' are specific, and the tool is distinct from sibling tools like 'fetch_order' or 'fetch_all_open_positions'.

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 alternatives. With many fetch-related sibling tools, explicit differentiation (e.g., 'Use for high-level overview; use fetch_historical_order_data for detailed history') is missing.

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