check_balance

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a read-only operation, what data structure or format is returned (e.g., numeric value, currency object), or whether the balance is real-time versus cached. The term 'Check' implies reading but does not confirm safety characteristics.

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 with the action verb front-loaded. There is no redundant or wasteful text, and every word serves to clarify the tool's function.

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?

While adequate for a zero-parameter tool, the description is incomplete given the presence of multiple financially-related siblings (budget, get_ledger, spend, get_payment_url) and the lack of an output schema. It should clarify how this relates to other financial tools and hint at the return structure.

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, the baseline score applies per the rubric. The schema requires no additional semantic explanation, and the description correctly implies no user input is needed to retrieve the organization's balance.

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 uses a specific verb ('Check') and identifies the resource ('current credit balance') and scope ('organization on Rhumb'). However, it does not explicitly differentiate from siblings like 'get_ledger' or 'budget' that may also return financial information, falling short of a 5.

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 such as 'get_ledger' (which may show transaction history), 'budget', or 'spend'. There are no prerequisites, conditions, or exclusion criteria mentioned.

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