get_check_account_balance

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the retrieval action without clarifying that it is read-only, what the reply format is, or any special behavior (e.g., caching, real-time). Minimal transparency.

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?

Single sentence containing exactly one verb and one noun phrase. No fluff, efficiently conveys the tool's purpose. Slightly underspecified but not wasteful.

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 2 parameters (one undocumented in description), no output schema, and no annotations, the description leaves significant gaps: return value type, error handling, meaning of 'balance', and interaction with optional date. Incomplete for a safe agent usage.

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 description coverage is only 50% (only 'checkAccountId' documented). The description adds no insights about the 'date' parameter, such as its format or optionality. Does not compensate for missing schema documentation.

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 'Get the current balance of a check account' uses a specific verb ('Get') and resource ('balance of a check account'), making the purpose clear. It differentiates from sibling tools like 'get_check_account' which likely returns full account details.

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 guidance on when to use this tool versus alternatives such as 'get_check_account' or 'list_transactions'. The description lacks any context about prerequisite conditions or scenarios where this tool is preferred.

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