Update Bank Account

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

Description aligns with annotations (write, idempotent, non-destructive) and adds context about partial update behavior and specific updatable fields, enhancing transparency beyond 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?

Two-sentence description is highly concise, front-loads purpose and editable fields, with no unnecessary information.

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 moderate complexity and good schema/annotations, the description covers purpose and partial update behavior but omits return values or error conditions, which are minor gaps.

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 has 100% coverage, but description adds value by clarifying that all fields except 'id' are optional for partial updates, going beyond the schema's information.

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 clearly states the tool updates a company bank account, enumerating specific editable aspects (rename, account number/SWIFT/bank, show on invoices) and distinguishes from sibling tools like create_bank_account and delete_bank_account.

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 for partial updates via 'Pass only the fields to change' but lacks explicit guidance on when to use versus alternatives or prerequisites beyond having an existing account.

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