borderou_transactions_save

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

No annotations are provided, so the description carries full burden. It does disclose the mutation behavior (creates payment records, updates invoice status), but doesn't disclose whether this is reversible, whether it can be called multiple times, whether it operates transactionally (all-or-nothing vs partial success), or what happens to already-paid invoices. For a persistence/save operation with zero annotation coverage, this is thin.

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, front-loaded with the primary purpose, minimal waste. Could arguably add a bit of behavioral context without bloating, but as written it's efficient.

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?

This is a mutation tool with no annotations and no output schema. The description doesn't explain return values, error scenarios, idempotency, or whether the operation is atomic. Given it creates payment records and updates invoice status—a consequential financial operation—the description should provide more behavioral guidance.

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 coverage is 100%, so schema documents both parameters. The description adds the meaning of transactionIds (matched transaction matches to save) and companyId context (active company fallback exists in schema). Baseline 3 is appropriate since the schema already carries the load, and the description adds limited extra semantic value.

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 clearly states the tool saves and persists selected borderou transaction matches, creating payment records and updating invoice payment status. The verb 'Save' plus resource 'borderou transaction matches' is specific, though it doesn't explicitly differentiate from sibling tools like borderou_transactions_rematch or borderou_transaction_update.

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 does not state when to use this tool versus alternatives like borderou_transactions_rematch or borderou_transactions. It doesn't mention prerequisites (e.g., that matches must first be identified/loaded), nor does it explicitly exclude other tools or state what happens if called with unmatching IDs.

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