get_account_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. The verb 'Get' indicates a read operation, but the description does not elaborate on return format, error behavior, or whether the balance includes pending transactions. It discloses the fundamental read-only nature but lacks additional context.

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 sentence, front-loaded with the core purpose, and contains no superfluous words. It is appropriately sized for a simple single-parameter tool.

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?

For a tool with one parameter and no output schema, the description tells the agent exactly what it does and what input is required. However, the lack of output schema means the agent does not know the exact return structure (e.g., number vs. object), so it is not fully complete. Still, it covers the essential context for invoking the tool correctly.

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 already provides 100% coverage for the only parameter (account_id) with a clear description, so the baseline is 3. The description's 'by account ID' merely echoes the schema without adding new meaning, such as format constraints or default values.

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 resource ('account balance'), clearly distinguishing it from sibling tools like get_accounts (which lists accounts) and get_transactions. It also specifies the scope ('by account ID'), indicating a single-account lookup, so it is unambiguous.

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 implies usage when a specific account balance is needed, but it provides no explicit guidance on when to prefer this over alternatives like get_accounts or get_transactions. It does not mention any exclusions or alternative conditions, leaving the agent to infer the appropriate context from the tool name alone.

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