Log Transaction

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

The description adds meaningful behavioral detail beyond the annotations: it declares write semantics, external_id deduplication, Zelle currency constraints, mirror_event behavior with the ledger as source of truth, and the $0.10/API key requirements. This is valuable context that the minimal boolean annotations do not provide.

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 front-loaded with the core purpose and packs many necessary constraints into short, scannable clauses. There is no filler or repetition; every clause adds useful information.

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 description covers essential constraints and edge cases like deduplication, currency, mirror events, cost, and auth. Given the tool's high parameter count and low schema coverage, some parameter meaning is still missing, though the presence of an output schema likely reduces the need to describe return values.

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?

With only 32% schema description coverage, the description compensates for several key parameters: direction/type combos, positive amount, external_id deduping, optional project/tags, currency, and mirror_event. However, many of the 19 parameters remain undocumented in both the schema and the description, so the compensation is incomplete.

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 a strong verb and resource ('Income/expense/transfer write'), and enumerates the record types and key use cases like Venmo/Stripe/refunds. It does not explicitly name sibling tools like log_income or log_expense, so it is clear but does not explicitly differentiate from those alternatives.

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 gives concrete situational guidance, such as 'direction=from + type=income for Venmo/Stripe/refunds received', 'external_id dedupes imports', and 'Zelle always USD', which help an agent decide how to invoke it. However, it does not explicitly state when NOT to use it or which sibling tool to prefer.

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