brc_list_supplier_op_bal_trans

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

No annotations provided. The description states it is a read operation ('Gets'), but does not disclose any other behavioral traits such as pagination, sorting, or handling of empty results. The agent has no additional context beyond the tool being read-only.

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?

A single concise sentence with front-loaded verb and resource. No wasted words, but could provide more useful guidance without becoming verbose.

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 low complexity and 100% schema coverage, the description is adequate but incomplete. It lacks details on output format, pagination, or error conditions. For a simple list tool, it is minimally viable.

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 100% for both required parameters (companyName and itemId). The description adds no extra meaning beyond the schema. 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 clearly states the verb 'gets' and the resource 'supplier's opening balance transaction list'. It distinguishes from siblings like brc_get_supplier_opening_balance (which likely gets the balance amount) and brc_list_supplier_account_trans (which lists all account transactions). However, it does not explicitly differentiate itself.

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?

No guidance on when to use this tool vs alternatives. No mention of context like prerequisites or when to prefer this over list_supplier_account_trans or get_supplier_opening_balance.

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