Retrieve your balances

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered structurally. The description adds meaningful context by disclosing that values come from a double-entry ledger and defining each balance category, but it says nothing about freshness, caching, currency, or snapshot timing for a read tool whose whole value is numeric accuracy.

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?

Front-loaded with the core statement followed by a compact, scannable definition list for each balance field. The opening line largely repeats the tool title, which is a small redundancy, but the rest is dense and earns its space.

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?

With no output schema, the field-by-field definitions are exactly the compensation needed, and the returned shape is now inferable. Remaining gaps are minor: it does not say whether balances are per-currency or aggregated, or how the 'total' interacts with 'settled_total' across currencies.

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 is 4 and there is nothing further to document. The schema is closed with additionalProperties=false, which the description does not need to restate.

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 ('Retrieve your balances') and scopes it to 'this mode', implying account-level rather than subaccount balances. It never names the nearby sibling get_subaccount_balance, so an agent must infer the distinction rather than being told it.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative routing to get_subaccount_balance or get_settlement. The phrase 'in this mode' is the only contextual hint and is never explained.

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