updateScheduledTransaction

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

With no annotations, the description carries the full burden. It only states 'Updates a single scheduled transaction', failing to disclose behavioral traits such as whether the update is partial or full, idempotency, authorization requirements, or side effects.

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?

The description is a single sentence with no unnecessary words. It is concise but could benefit from a bit more detail without becoming verbose.

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 the tool has 3 parameters (one nested), no output schema, no annotations, and many siblings, the description is too sparse. It does not explain the update semantics or how to use the parameters effectively.

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?

The schema description coverage is 67%, and the description adds no additional meaning beyond the schema. It does not summarize the role of plan_id, scheduled_transaction_id, or the nested scheduled_transaction object. Baseline 3 is appropriate as the schema provides most information.

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 explicitly states 'Updates a single scheduled transaction', clearly identifying the action (update) and the resource (scheduled transaction). It distinguishes itself from sibling tools like createScheduledTransaction, deleteScheduledTransaction, and getScheduledTransactionById.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to update vs. create or delete. There is no mention of prerequisites, limitations, or context like the need for a valid plan or transaction ID.

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