update_transactions_bulk

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

Annotations provide 'idempotentHint: true', and the description adds behavioral constraints beyond that: maximum 500 items, each must include id and a writable field, and prohibition on split/grouped transactions. No contradictions. The description adds meaningful context about the operation's constraints.

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 three sentences, front-loaded with the purpose, and contains no unnecessary words. Every sentence adds essential information.

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?

For a bulk update tool with no output schema and a complex input schema, the description covers the key constraints (range, required fields, exclusions). It could mention error handling or idempotence implications, but with annotations covering idempotence, the description is sufficiently complete.

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%, and the description adds value by stating that each entry must include 'id' plus at least one writable field, which is not enforced by the schema (only 'id' is required). This clarifies the intent beyond what the schema defines.

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 verb 'Update', the resource 'multiple transactions', and specific constraints: batch size 1-500, each entry must include 'id' and a writable field. It also explicitly says what it cannot do (modify split or grouped transactions), distinguishing it from siblings like 'update_transaction' (single) and 'delete_transactions_bulk'.

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 provides clear context for when to use (updating multiple transactions in bulk) and explicitly states an exclusion ('Cannot be used to modify split or grouped transactions'). While it does not name alternative tools, the constraint is sufficient for an agent to infer when to avoid this tool.

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