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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on semantics: the +/− sign convention for direction of debt, and the fact that results are split into loans, contributions, unreimbursed expenses and unspecified owner money. It does not say whether results are aggregated or per-company rows beyond the vague 'rows behind it'.

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?

One packed sentence with no filler, and the core idea ('what each company owes') is front-loaded. The trailing clause 'with the rows behind it' is vague and slightly weakens an otherwise efficient statement.

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 description carries the return-value burden and does so reasonably: it enumerates the four balance categories, the sign convention, and hints at underlying rows. It omits currency, aggregation level, and record counts, which leaves minor gaps for a no-output-schema financial read tool.

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 100% and the single optional 'company' parameter already documents the accepted values ('company name or id, Personal, all', omit for everything visible). The description adds nothing about the parameter, so the baseline 3 applies.

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 names the resource (owner balance per company) and the scope (the person behind this connection), plus the sign convention and the four breakdown categories. An agent can distinguish it from list-style siblings, though it never explicitly positions itself against lookalikes like get_liabilities or get_holdings.

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 statement, no prerequisites, and no named alternative. The closest thing to guidance is the phrase 'what each company owes the person behind this connection', which only implies the use case. An agent must infer when this beats get_liabilities or get_overview.

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