list_bank_account_transactions

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

With no annotations provided, the description carries the full burden. It only restates the action and provides no behavioral details such as read-only nature, default ordering, or that limit/offset are used for pagination. No contradictions, but minimal disclosure.

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 declarative sentence, front-loaded with verb and resource. No wasted words, appropriately sized for a simple list operation.

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?

The description, combined with the schema, is adequate for a simple list tool: it identifies the required resource and there is an output schema, so return values are covered. However, it lacks guidance on pagination semantics, when to use this tool, and any behavioral caveats that an agent would need for correct invocation.

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%. The description only indirectly references bank_account_id ('specific bank account') and provides no explanation of limit or offset parameters. Names suggest pagination, but the description doesn't confirm or add meaning beyond 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?

States the specific action (list transactions) and scope (for a specific bank account). The verb 'list' with resource 'transactions' clearly distinguishes from singular retrieval tool get_bank_account_transaction and other transaction list tools.

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?

Implies usage by stating the purpose but provides no explicit guidance on when to use this vs alternatives like get_bank_account_transaction, nor any exclusions or pagination strategy.

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