fiken_list_account_balances

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

The annotation readOnlyHint:true already signals a safe read operation. The description adds that it retrieves accounts and closing balances, which is consistent. However, it does not disclose any behavioral details such as whether the results are paginated or the order of accounts. The description is adequate but not rich.

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 sentence that is concise and front-loaded with the action. Every word is necessary and there is no superfluous text.

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 the tool has 5 parameters, no output schema, and sibling tools, the description is too minimal. It does not explain that the result is a list, that filtering by account ranges is possible, or the nature of closing balances. Agents would benefit from more details about the return structure and filtering capabilities.

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 only 20% (only the 'date' parameter is described). The description mentions 'for a given date' but does not explain the other parameters (page, pageSize, fromAccount, toAccount). With low coverage, the description should have compensated by describing these parameters, but it did not.

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 verb 'retrieves', resource 'accounts and closing balances', and condition 'for a given date'. It distinguishes from similar siblings like fiken_get_account_balance (which retrieves a single account's balance) and fiken_list_accounts (which lists accounts without balances).

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 implies that the tool is used to get closing balances for all accounts on a specific date, but it does not explicitly state when to use it versus alternatives like fiken_get_account_balance or fiken_list_accounts. No exclusion criteria or prerequisites are mentioned.

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