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

With no annotations, the description carries the full behavioral burden and does well: oldest-first ordering, no paging, CompanyMember read permission, the auto_created/ownership_status/needs_ownership_review lifecycle, and the explicit null-vs-zero distinction for statement_count/entry_count. The only gap is that read-only nature is implied by 'list' rather than stated.

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-loads purpose in the first sentence and every subsequent sentence carries operational value (ordering, return fields, null semantics, how to set the ledger code). Slightly dense, but nothing is padding.

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 list tool with no output schema and no annotations, the description documents return fields, ordering, paging behavior, permission level, and the meaning of special fields — everything an agent needs to call and interpret 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?

Schema description coverage is 0% and the sole parameter company_id is undocumented in the schema. The description implies company scoping ('the company's bank accounts') and the read permission, but never states the expected id format, so it only partially compensates for the coverage gap.

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 and resource (the company's bank accounts) and pins the exact key it returns (bank_account_id) plus who consumes it (statement import, bank-entry list, reconciliation). An agent can distinguish it from siblings like list_bank_entries or get_bank_status without opening a schema.

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?

Explains the ordering and that there is no filter or paging, and routes to the single-account GET /bank-accounts/{account_id} for counts. It names the workflows that depend on the returned id, giving clear context, but stops short of explicit when-not-to-use exclusions against sibling list tools.

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