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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds one useful behavioral nugget — that the returned ids feed downstream tools — but says nothing about result shape, ordering, or behavior when no bank is linked (the output schema covers the payload).

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?

A single sentence that leads with the verb and resources and packs the downstream-id note into a tight parenthetical. No restatement of the title and no filler.

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 simple idempotent read-only listing tool with full annotation coverage, a documented single param, and an output schema describing the return payload, the description supplies everything an agent needs to select and call it correctly.

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?

Only one optional parameter (ledger), and the schema documents it at 100% coverage including the unpinned-credential default. The description adds nothing about it, which is acceptable given the schema does the work, but there is no added meaning.

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 both resources (bank connections and their accounts), plus names the exact identifier fields returned (item_id, account_id). This clearly separates it from siblings like listStagedBankTransactions or reconcileBankAccounts, which operate on staged transactions or reconciliation work rather than the connection inventory.

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?

It implies the usage context by flagging that these are the ids that bank sync, import, and connection tools consume, which tells an agent to call this first in those flows. It stops short of explicitly naming which sibling to call instead or stating exclusions, so it lands just below the top band.

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