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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: only confirmed payments are counted, departed members still appear with left: true, and net_pending_minor includes unconfirmed payments. It stops short of noting scope/permission requirements, but the added semantics are substantial.

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 sentences with no filler, and the core output semantics are front-loaded before the edge-case notes about left members and pending balances. Dense but every sentence carries information.

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?

An output schema exists, so return structure need not be described, yet the description helpfully explains the sign convention and edge cases (left: true, net_pending_minor). Combined with annotations covering read-only safety, an agent has enough to call this correctly; only the relationship to sibling balance/settlement tools is missing.

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 0% and the single group_id parameter is never mentioned in the description. The parameter's name, uuid format, and required status make it essentially self-explanatory, but the description adds no meaning over the schema, so a baseline 3 is appropriate.

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 states precisely what the tool computes: net balance per member with sign convention (positive = others owe them), plus pairwise debts, limited to confirmed payments. That is a specific verb+resource. It does not distinguish itself from the sibling get_settlement_plan, which is the nearest alternative, so it falls short of a 5.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as get_settlement_plan or list_payments. The agent must infer that this is the right call for reading group balances purely from the name and return-value description.

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