update_scheduled_transaction

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

Discloses important behavioral traits: frequency single-word limitation (explains API rejection and workaround via UI), and dry_run for validation. No annotations provided, so description carries burden. Lacks details on authorization, idempotency, or side effects, but covers key points.

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?

Concise and well-structured: one-line purpose, a usage guideline, then a clear argument list. No unnecessary words. Every sentence adds value.

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?

Covers essential aspects for an update tool with 11 parameters and an output schema. Explains frequency limitation and dry_run. Could include usage example or error scenarios, but overall adequate.

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?

Adds meaning beyond schema: each parameter is described (e.g., 'New first date (YYYY-MM-DD)', 'New dollar amount', 'Scheduled transaction UUID'). Schema coverage is 0%, so description compensates well. Could clarify flag_color possible values, but overall informative.

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 fields of an existing scheduled transaction' with a specific verb and resource. It distinguishes from sibling tools like create_scheduled_transaction and delete_scheduled_transaction.

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?

Provides explicit guidance: 'Only provide the fields you want to change.' Also details frequency constraints and the dry_run parameter. Could improve by explicitly stating when not to use this tool versus alternatives, but the context is clear.

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