update_transaction

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

Discloses partial update behavior and restriction on certain fields, plus auth requirement. But lacks details on return value, error handling, atomicity, or side effects. Annotations absent, so description carries burden but remains incomplete.

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, no redundancy. Every sentence adds value: first defines action, second provides critical restriction. Very concise and well-structured.

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 core functionality, restrictions, and auth. Missing return value description and validation behavior. Given lack of output schema and annotations, it is fairly complete but could mention that the transaction must exist.

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 50% with nested object; description adds that only supplied fields are changed and that certain fields are immutable. No detailed explanation of each patch property beyond schema names. Adequate but not exceptional.

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?

Clearly states verb 'Update' and resource 'transaction', specifies partial update ('Only the fields supplied are changed'), and explicitly states what cannot be changed. Distinguishes from siblings like delete_transaction and record_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?

Explicitly tells when not to use (cannot change card identity/type, must delete/recreate) and mentions auth requirement (IWMM_API_KEY). Does not explicitly mention alternatives, but the restriction implies when to use record_transaction or delete_transaction.

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