Create bank account

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

Annotations indicate write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description aligns by stating 'Create...' and notes return behavior ('Returns the new account with its id'). Adds context about currency (AUD-only) and default opening balance, but does not contradict annotations.

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?

Four sentences with no wasted words. Front-loaded with verb and resource, followed by usage case, prerequisite check, and follow-up. Efficient and well-structured.

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 11 parameters and no output schema, the description provides essential behavioral context: return value (id), currency limitation, default opening balance, and workflow steps. Slightly incomplete as it doesn't explain all parameters, but overall adequate for an experienced user.

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 91%, so parameters are well-documented. Description adds overall context but does not significantly enhance per-parameter understanding beyond what schema already provides. Baseline of 3 is appropriate.

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?

Tool description clearly states it creates a new cash/bank account under a fund for tracking and reconciling. It provides examples (nabtrade cash hub, term deposit, operating account) and distinguishes from sibling tools like list_bank_accounts and record_cash_transaction by mentioning them in context.

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?

Explicitly states when to use ('when a statement or CSV belongs to an account the fund doesn't have yet') and advises checking list_bank_accounts first to avoid duplicates. Also recommends following up with record_cash_transaction to load movements, providing a clear workflow.

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