createTransaction

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

No annotations provided, so description carries full burden. It discloses that future dates are not permitted, and explains the effect of `import_id` on matching. It does not cover error handling or rate limits, but the key behavioral constraints are clear.

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?

Two sentences clearly state purpose, mode distinction, and key restriction. No wasted words; front-loaded with main action.

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?

Given complexity (nested objects, multiple modes, sibling tools), the description covers core behavior, restrictions, and mode differentiation. No output schema, so return values not expected. Could mention plan_id requirement but it is in required fields.

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 only 33%, but the schema itself provides detailed descriptions for many nested parameters. The description adds the high-level single vs multiple distinction and the prohibition on future dates, but does not provide additional semantic meaning beyond what the schema already offers for individual parameters.

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?

Description clearly states 'Creates a single transaction or multiple transactions' with specific verb and resource. It differentiates between single and multiple by body structure (`transaction` object vs `transactions` array). It also explicitly excludes scheduled transactions, distinguishing from sibling `createScheduledTransaction`.

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?

Description explains when to use single vs multiple mode and explicitly states that scheduled transactions (future dates) cannot be created, implying use of `createScheduledTransaction` for those. It does not mention alternatives like `importTransactions` but is clear enough for common scenarios.

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