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

readOnlyHint already declares this a safe read, so the description's contribution is the scoping word 'every' (no filtering, all accounts) and the endpoint reference. It says nothing about ordering, pagination, or whether multi-currency balances are included — modest added context beyond annotations.

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?

Two short sentences, purpose front-loaded, endpoint detail second. Nothing wasted and nothing repeated from the title alone.

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?

A simple no-parameter read with no output schema; stating scope and endpoint is nearly sufficient. A brief note on what each balance entry contains (or that results are unfiltered/unpaginated) would close the remaining gap.

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?

Zero parameters, so the baseline of 4 applies; the description correctly conveys that the call takes no filtering input by saying 'every' account.

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 a specific verb and resource: 'Get the balance of every cash and bank account', plus the underlying endpoint. It is distinguishable from kledo_list_bank_transactions (transactions, not balances) and kledo_list_accounts (accounts, not balances), though it doesn't name those siblings explicitly.

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?

Usage is only implied by the resource name; there is no statement of when to prefer this over kledo_list_accounts or kledo_report_cash_flow, and no prerequisites or exclusions. An agent can infer intent but must decide among siblings on its own.

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