Add transactions

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

Annotations declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's added value is the return contract — created transactions, updated balances, duplicate warnings — and the fact that categories are auto-filled from payee history or ZenMoney suggestions. That is meaningful disclosure beyond the annotations, though batch size limits are not mentioned.

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 dense sentences, front-loaded with what is recorded, followed by amount/category rules and then the return contract. No filler and nothing buried.

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?

With no output schema, the description correctly describes return values (created transactions, balances, duplicate warnings) and covers categorization behavior. Gaps are minor: the 50-item batch cap and dry_run preview are left to the schema.

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?

At 67% schema coverage the description still adds real meaning: amounts are always positive in the account currency, transfers are between the user's own accounts, and category resolution falls back to payee history/suggestions when omitted. It complements rather than repeats 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?

Specific verb (Record) plus resource (transactions) with the full set of supported types enumerated, including a plain-language gloss of debt_out vs debt_in. An agent can immediately tell this creates ledger entries rather than accounts or budgets.

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?

Usage is implied (this is the tool that writes transactions) and the auto-categorization default is stated, but no sibling is named as the alternative for editing or reversing entries (e.g. update_transactions vs delete_transactions). No explicit when-to-use or prerequisite guidance.

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