Создать или изменить счёт

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

Adds significant behavioral context beyond the annotations: currency is fixed per account and determines all operation currencies, the current balance cannot be edited because it is derived from operations, and only the initial balance can be changed. No contradiction with 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?

Three compact sentences cover the core semantics without repetition. The create/update distinction is front-loaded, followed by currency and balance rules; no filler.

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 mutation tool with 11 parameters and no output schema, the description covers the key business rules and mode selection. It leaves details like account_type being required on creation to the schema, which is acceptable given full schema coverage.

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 100%, so the baseline is 3. The description goes beyond the schema by explaining the implications of currency and the distinction between initial and current balance, adding real value for the account, currency, and initial_balance parameters.

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?

States a clear verb and resource: creates a new account when no account is provided and edits an existing one when an account is specified. However, with the sibling account_update also available, it does not explicitly distinguish why one would choose accounts_save over account_update for edits.

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?

Provides clear conditional usage: omit 'account' to create, specify it to update. This is strong guidance for the tool's two modes, though it does not discuss alternatives such as account_update or any exclusions.

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