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

Annotations already flag destructive, idempotent, and non-read-only behavior, but the description adds valuable detail: it creates a signed ADJUSTMENT transaction for the difference, is a no-op when unchanged, rejects exchange-managed accounts, and requires confirmation. There is no contradiction with the 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 are front-loaded with the action and then cover side effects, constraints, and execution requirements. Every sentence adds useful information with 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 destructive balance mutation with no output schema, the description supplies the key behavioral details an agent needs: adjustment transaction creation, no-op behavior, account-type exclusion, and the confirmation requirement. It is complete enough to call 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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds meaning beyond the schema by explaining the consequence of the balance value and the no-op behavior when unchanged, though it leaves idempotencyKey entirely to the schema.

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 and resource: set an account's balance to a new value. It also explains the resulting side effect, a signed ADJUSTMENT transaction for the difference, which distinguishes it from add_transaction and reconcile_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?

It gives clear usage context by requiring confirmation: true and explicitly rejecting exchange-managed accounts as a when-not condition. It does not name sibling alternatives such as reconcile_account, so it falls short of full alternative routing guidance.

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