brc_list_bank_accounts

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

With no annotations and a one-line description, behavioral traits like pagination, rate limits, or whether the operation is read-only are entirely omitted. The description adds no transparency beyond the name.

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 extremely short (one sentence), but it is under-specified rather than concise. It lacks essential details expected for a list operation with seven parameters.

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?

Given seven parameters, no output schema, and no annotations, the description fails to explain pagination, filtering, required fields, or return behavior. It is far from 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 description coverage is 43%, leaving many parameters (top, page, skip, pageSize) undocumented in both schema and description. The description adds zero information about parameters, failing to compensate for the schema gaps.

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 'Lists BRC bank accounts' clearly states the verb and resource. It differentiates from sibling tools like brc_get_bank_account (single) and brc_list_accounts (different entity), though it is minimal.

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?

No guidance on when to use this tool versus siblings such as brc_list_accounts or brc_get_bank_account. No context on prerequisites or conditions for use.

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