broker_sync_balances

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only or triggers a sync/mutation, not auth requirements, not rate limits, not data freshness or normalization semantics despite using the word 'normalized'.

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?

The body is a verbatim duplication of the same sentence twice, with no front-loaded verb and no additional information in the second copy. That is redundancy rather than concision.

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 annotations and no output schema, the description is the only source of behavioral and return-shape information, and it provides almost none — not the response structure, not whether results are paginated or per-account keyed. Only the general subject matter is conveyed.

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 coverage is reported at 100% for the single user_id parameter, so the schema does the documentation work. The description adds no meaning about user_id scope or how it relates to connected accounts, so the baseline of 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 it concerns (cash & buying power per connected account, normalized), which is more specific than the bare tool name. However, it supplies no verb — an agent cannot tell whether this fetches, computes, or pushes/syncs balances — and it does nothing to separate this from siblings like broker_sync_positions or broker_sync_transactions.

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 guidance on when to call this versus the other broker_sync_* tools, no prerequisites, and no exclusions. The agent is left to infer usage entirely from the name.

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