add_balances

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

No annotations, so description bears full burden. Discloses overwrite semantics, return format (counts grouped by period), currency default, and FX conversion. Does not mention permissions or rate limits, but overwrite is the key behavioral trait.

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?

Four sentences, each serving a purpose: what it does, when to use, how it behaves, currency note. No filler or redundancy.

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?

Given complexity of bulk-upsert with nested entries, the description covers core behavior, usage scenario, and return info. No output schema, but return format is hinted. Sibling tools are many, but this is well-differentiated.

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%, so description must compensate. It adds meaning beyond schema: explains overwrite key fields, currency default, FX conversion at date. Schema already describes field types and enums, but description provides operational context.

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 clearly states it is a bulk-upsert for balance sheet entries (assets + liabilities) across months and categories. It distinguishes from siblings like add_balance (singular) and add_flows by specifying the bulk and balance sheet nature.

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?

Provides a concrete use case: importing a net-worth spreadsheet. Explains overwrite behavior on duplicate key. Lacks explicit when-not to use or alternatives, but the context is clear.

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