list_bank_accounts

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

With no annotations provided, the description bears full responsibility for behavioral disclosure, but it merely restates the tool's name without explaining pagination, return structure, side effects, or read-only nature. It adds no behavioral insight beyond what the name already conveys.

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, front-loaded sentence with no wasted words, which is highly efficient. However, its extreme brevity sacrifices substance, omitting critical parameter and behavioral context.

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 that the tool has two pagination parameters and an output schema, the description is too sparse to be fully actionable. It fails to clarify default behavior or how the parameters control listing, making it incomplete for an agent to invoke correctly without additional inference.

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 description does not mention the 'limit' and 'offset' parameters at all, and schema description coverage is 0%. Since the description should compensate for the schema's lack of descriptions, this is a significant omission that leaves parameter semantics unexplained.

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 a specific action ('List') and resource ('bank accounts'), and names the source system ('Buildium'). This effectively distinguishes it from sibling tools like list_bank_account_transactions and get_bank_account, making the purpose 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?

The description provides no guidance on when to use this tool versus alternatives such as get_bank_account or list_bank_account_transactions. It neither states explicit use cases nor excludes any scenarios, leaving the agent without contextual direction.

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