manage_transaction

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It does disclose action-specific requirements and the meaning of amount sign (positive=debit, negative=credit), which is useful. However, it does not explain update semantics (e.g., whether omitted fields are unchanged or cleared), delete irreversibility, or expected return values, leaving meaningful gaps given the lack of 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?

The description is highly concise and well-structured. It front-loads the primary purpose in a single sentence, then uses bullet-style action-specific lines to convey the required parameters without redundant commentary. Every sentence contributes directly to operational guidance.

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?

The tool has moderate complexity (11 parameters, three distinct actions) and no output schema or annotations, so the description must carry significant weight. It covers the main actions well but fails to mention the 'manual_account_id' parameter entirely and incorrectly names it 'account_id' in the create instructions. This omission and mismatch leave the description incomplete for a full parameter set.

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?

The schema already provides 100% description coverage for all 11 parameters, so the baseline is 3. The description adds value by grouping parameters by action and clarifying the amount sign, but it also introduces a mismatch: it references 'account_id' in the create action, while the schema defines 'manual_account_id'. This error undermines the added semantics, leaving the score at the baseline rather than above.

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 opens with 'Create, update, or delete a single Lunch Money transaction,' which uses a specific verb (create/update/delete) and a clear resource (Lunch Money transaction). The qualifier 'single' distinguishes this from sibling tools like bulk_update_transactions, split_transaction, and group_transactions, so the purpose is unambiguous.

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 provides explicit instructions for each action, listing required and optional parameters per operation. This gives clear context for when to use each mode. However, it does not explicitly mention alternatives like bulk_update_transactions for batch operations, nor does it state when not to use this tool, so it falls short of a 5.

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