SellerWallet_listAccountBalances

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

No annotations are provided, so the description must carry behavioral disclosure. It usefully reveals that the tool is a catalog entry that executes remotely ('Runs in your Kuudo deployment, not here'), which is significant. However, it does not mention read-only status explicitly, error behavior, authentication needs, or whether the call has side effects, though 'Retrieve' weakly implies a read.

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 very short and wastes few words. The first sentence 'Catalog entry' is terse but adds context, and the second sentence gives the purpose. A small amount of clarity is lost because 'Catalog entry' and 'not here' overlap, and 'given account' introduces ambiguity without elaboration.

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 the zero-parameter schema and no output schema, the description is relatively lean. It conveys the tool's purpose and remote execution context, but it does not describe the return format or how the 'given' account is selected, which could prevent an agent from using it correctly even in the Kuudo deployment.

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?

With zero parameters and an empty schema, the baseline is 4, but the description's phrase 'in a given Seller Wallet bank account' implies an input for specifying the account without any schema support or explanation. The schema has additionalProperties true, yet no parameter name or format is provided, leaving the agent to guess how to identify the account.

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 states a clear action and resource: 'Retrieve the balance in a given Seller Wallet bank account.' It distinguishes from nearby siblings by specifying 'balance' rather than account details or transactions, though it does not explicitly name any alternative tool.

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?

The phrase 'Runs in your Kuudo deployment, not here' gives an important environmental exclusion that tells the agent this tool is not callable in the current context. However, it does not explain when to prefer this tool over related tools like SellerWallet_getAccount or SellerWallet_listAccountTransactions, leaving selection logic mostly implicit.

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