Reconcile account balance

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

Annotations already establish readOnlyHint=false, idempotentHint=true, and destructiveHint=false, matching the 'make it match reality' framing. The description adds real value beyond them: it discloses that a correction transaction is created and that computation depends on freshly synced data. It doesn't cover permissions or what happens for an unknown account, keeping it out of 5 territory.

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?

A single front-loaded sentence with no filler; the core action leads and the qualifying clause follows. Every part earns its place.

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 an idempotent mutation tool with no output schema, the description conveys the mechanism, the sync dependency, and the record type created. It leaves minor gaps around permissions and side effects, but nothing essential to invoking it correctly is missing.

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 already 80%, with account, actual_balance, date, comment, and category all documented inline. The description adds only the notion that the correction is income-or-expense in nature, which loosely relates to category but gives no syntax or format detail beyond the schema. Baseline 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?

States a specific verb+resource (adjust/reconcile the account balance) and explains the mechanism: recording the difference as an income/expense correction transaction. This is more than a restatement of the name, though it doesn't explicitly contrast itself with create_transactions, which could also produce a correcting entry.

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?

Gives a clear condition for use ('make an account balance match reality') and a prerequisite hint ('computed against freshly synced data'), which nudges the agent toward the sync tool first. It stops short of naming alternatives or stating when not to use it.

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