get_bond_balances

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description does not explicitly state safety, return format, or any limitations. For a tool with zero annotations and no output schema, this is a significant gap.

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 description is a single, efficient sentence that avoids redundancy and front-loads the action. It is appropriately sized for the tool's simplicity.

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 should clarify what the response contains or how it interacts with other portfolio tools. The absence of any mention of return structure, scope, or relationship to get_all_portfolios leaves the agent with incomplete information for a complete request.

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 has zero parameters, so the description does not need to document parameter semantics. The baseline of 4 is appropriate because there are no parameter-related ambiguities to resolve.

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 the tool retrieves bond and government securities holdings, using the explicit verb 'Get' with a specific resource. It distinguishes itself from sibling tools like get_cash_balances and get_equity_balances by asset class, and the parenthetical 'Obligasi / SBN' adds clarity for Indonesian government securities.

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?

Usage context is implied by the asset class and sibling structure—users would select this for bond holdings rather than equities or cash. However, there is no explicit when-to-use guidance or indication of how this differs from get_all_portfolios, which may also include bond positions.

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