account_balance

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully explains that the operation is asynchronous and returns a pipe-delimited string per account type via callback. However, it misses other behavioral aspects such as required permissions, error handling, or the role of the resultUrl parameter, so transparency is moderate.

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 two sentences, each adding value: the first states the core purpose, the second explains the asynchronous callback behavior. There is no wasted wording, and it is front-loaded with the main action.

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?

No output schema exists, so the description must explain the return result. It mentions the pipe-delimited string per account type, which is helpful, but it lacks parameter semantics and detail about how the callback is delivered or correlated. For a query tool, this is adequate but leaves clear gaps.

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 schema has 0% description coverage, and the description does little to clarify the three parameters (remarks, resultUrl, shortCode). It implicitly hints at resultUrl through the asynchronous callback, but it never explicitly explains what each parameter does or how they relate to the balance query.

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 queries the balance of a M-Pesa business account, using a specific verb ('Query') and a precise resource. This distinguishes it from sibling tools like transaction_status or query_org_info, which target different data.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or contexts where this tool is preferred. The only hint is that it queries balance, but no explicit usage direction is given.

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