Update Scheduled Transactions

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

Annotations indicate a write operation with idempotency and no destruction. The description adds that updates are undoable and reveals per-update API cost, providing context beyond 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?

Two concise sentences front-load the purpose and add critical behavior/cost info without redundancy. Every sentence earns its place.

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 purpose and key behaviors but omits return values, error conditions, and the 50-item array limit from schema. For a write operation with nested parameters, more completeness would help.

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 50%, but the tool description adds no parameter details. It fails to explain the transactions array structure or individual fields, leaving the agent underinformed.

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 'Update one or more scheduled transactions,' specifying the verb and resource. It distinguishes from siblings like create and delete, but could better differentiate from update_transactions for regular transactions.

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 notes that each update is undoable and costs one API call, and mentions no bulk endpoint exists. However, it does not explicitly guide when to use this tool versus create or delete alternatives.

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