fiken_list_bank_balances

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

The description 'Retrieves' aligns with the readOnlyHint annotation, so no contradiction. However, it adds minimal behavioral context beyond what annotations provide. It does not disclose pagination behavior, authentication needs, or the fact that it returns a list—though some of these may be inferred from the input schema.

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, concise sentence that contains no unnecessary words. It is front-loaded with the primary action and resource.

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 no output schema and a simple tool, the description is adequate but incomplete. It does not describe the return format (e.g., a list of balances with account details) or the effect of pagination parameters. It meets the minimum viable threshold for a read-only 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 coverage is only 33% (only 'date' has a description in the schema). The tool description does not explain the 'page' or 'pageSize' parameters, leaving them undocumented. Since coverage is low, the description should compensate but fails to do so.

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 tool retrieves bank balances for a company at a given date. It uses a specific verb ('Retrieves') and resource ('bank balances'), but does not differentiate from sibling tools like fiken_get_account_balance or fiken_list_bank_accounts, which could be confused.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or what other tools (e.g., fiken_list_account_balances) might be more appropriate for similar tasks.

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