SellerWallet_listAccountTransactions

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

With no annotations, the description carries the behavioral burden; 'Retrieve' makes clear this is a read operation intended to list transactions. It also adds the 'Runs in your Kuudo deployment, not here' execution context, but it doesn't disclose pagination, filtering behavior, or whether a bank account must already exist or be accessible.

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 short and scannable in three sentences, with the key action clearly stated. 'Catalog entry' is arguably filler, but the overall size is appropriate and the meaning is not buried.

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 list operation with no output schema, no pagination/filter guidance, an implied but unspecified account identifier, and numerous SellerWallet siblings, the description leaves too much to inference. An agent cannot tell the return shape, limits, or required account scope from this description alone.

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?

The schema has zero properties, so the 'given Seller Wallet bank account' phrase is the only semantic guidance, but it doesn't name or format the required identifier. The description adds meaning beyond the empty schema but is not actionable enough to fully compensate for the mismatch.

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 core sentence uses a specific verb ('Retrieve') and a clear resource ('list of transactions for a given Seller Wallet bank account'), which distinguishes it from getTransaction, getAccount, and listAccountBalances. The opening 'Catalog entry. Runs in your Kuudo deployment, not here.' is not purpose-related and slightly muddles the message, but the main action is unambiguous.

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 choose this over SellerWallet_getTransaction or SellerWallet_listAccountBalances, and no exclusions or alternative routing. The only contextual hint is the 'Kuudo deployment' execution note, which says nothing about use cases.

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