account_balance

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

With no annotations, the description carries the full burden. It merely says 'Get the current account balance' and provides no behavioral details such as required permissions, real-time vs cached data, or what response format to expect. The word 'current' hints at recency but does not disclose other traits.

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, front-loaded sentence with no wasted words. It efficiently communicates the core action and resource.

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 there is no output schema, the description should clarify what the return value looks like, but it only says 'balance' without specifying whether it's a number, string, formatted currency, etc. It also does not explain how the optional currency parameter affects the result or what the default behavior is. Important context is missing.

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% because the only parameter 'currency' has an explicit description. The tool description adds no additional meaning to the parameter, but the schema fully documents it. This meets the baseline for high schema coverage.

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 (Get) and a clear resource (current account balance). It is unambiguous and distinguishes itself from sibling tools like account_price_list and account_configuration, as none of those claim to return the account balance.

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 when-to-use or alternative-exclusion guidance is provided. The description only states what it does, not when an agent should choose this over other account-related tools. There is no mention of prerequisites or distinctions from similar tools.

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