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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description adds useful scope context (all groups, per-currency netting, owed/owing totals), but says nothing about freshness, pagination, or whether 'top group balances' is capped.

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 tight sentences: the first front-loads scope and the enumerated return contents, the second gives a one-clause framing anchor. No filler, nothing repeated from the schema or annotations.

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 parameters, no output schema, and annotations covering the safety profile, the description carries most of the remaining burden and does so by enumerating the returned fields. It is slightly thin on which sibling to choose and on any limits to 'top group balances', but nothing needed to invoke the tool is absent.

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 tool takes zero parameters, so there is no parameter semantics for the description to carry; the baseline of 4 applies. Schema description coverage is 100% and empty, so no compensating detail is required.

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 balance summary) plus the scope ('across all groups') and the three data components returned, so an agent knows exactly what it fetches. It does not, however, distinguish itself from near-identical siblings like get_consolidated_balances or get_group_balances, which the 'across all groups' phrasing could equally describe.

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 statement of when to prefer this tool over get_consolidated_balances, get_group_balances, or get_monthly_summary, all of which appear to cover overlapping balance territory. The 'main dashboard' remark is descriptive context, not selection guidance.

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