List transactions

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

Annotations already indicate readOnlyHint=true, and description confirms it's a read operation. Adds behavioral details: amounts are decimal strings and the includeMerchants limitation, which are beyond annotation scope. No contradiction.

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 sentences with no filler. First sentence covers core purpose and constraints; second adds key format and condition details. Entirely front-loaded and efficient.

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?

Covers purpose, constraints, and parameter interactions well. Lacks description of output structure (e.g., fields, pagination) which would be helpful given no output schema. Adequate but could be more complete for a list operation.

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 has 100% coverage with descriptions for all 4 parameters. Description adds value by noting that accountNumber setting causes includeMerchants to be ignored, and clarifies that amounts are decimal strings (affects output interpretation).

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?

Description clearly states verb 'list', resource 'booked transactions', and key constraints (date range, optional account scope). It distinguishes from sibling tools like get_transaction (single transaction) and list_payments (different resource).

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?

Provides guidance on when to use (listing booked transactions) and an important condition: includeMerchants only supported when not scoped to an account. No explicit comparison to alternatives like get_transaction for single transaction retrieval, but the condition is helpful.

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