create_transactions

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

Annotations only provide idempotentHint=false; the description adds that duplicate transactions are skipped and that the response includes inserted transactions plus skipped duplicates, and states the per-call limit. It doesn't mention default side effects such as balance updates or rule application, though those are covered in the parameter descriptions.

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 short sentences that front-load the action and resource, then add the key constraint and return behavior. No filler or repetition of schema details.

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 rich schema covers parameter semantics and the description supplies the missing return-value information. It is slightly incomplete only in not flagging default mutating side effects, but those are inferable from skip_balance_update's description.

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?

All parameters already have detailed schema descriptions, so the description adds little beyond echoing the 1-500 array constraint. Baseline 3 is appropriate because the schema does the heavy lifting.

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 names a specific action ('Insert') and resource ('transactions'), and adds a batch-size range and return behavior. This clearly distinguishes it from sibling tools like get_transactions, update_transactions_bulk, and create_transaction_group.

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 makes the use case clear: call this when you need to add one or more transactions. It doesn't explicitly name alternatives or exclusions, but the verb and resource leave little ambiguity against the sibling set.

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