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

With no annotations, the description carries the full burden and does so: it documents each returned field's semantics (position as 0-based eval order with first-match-wins, isEnabled, matchCount/lastMatchedAt, pausedReason) and the engine's firing constraints (new bank/imported transactions only, never transfers, planned, or manual-account transactions, never retroactive).

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?

Front-loaded with purpose and the call-before-mutation guideline, then field semantics and firing rules. Every sentence is informative, though the single dense paragraph is long enough that the field definitions and firing constraints run together.

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?

There is no output schema, so the description's field-by-field explanation of the return shape is exactly the missing context an agent needs, and the firing-condition caveats close the remaining gap for a zero-input list tool.

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 tool takes zero parameters, so the baseline is 4. The description adds meaningful semantics about the returned data even though there are no input arguments to clarify.

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?

States a specific verb (List) and resource (transaction automation rules / rules engine), plus scope (of the user, ordered by evaluation order). It is trivially distinguishable from create/update/delete/reorder_transaction_automation siblings.

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 states when to call it: before updating, deleting, or reordering a rule, in order to get its id. This is actionable routing guidance rather than an implied use case.

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