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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description merely restates 'Lists' and adds no behavioral details that annotations don't provide, such as pagination defaults, response format, or the fact that companyName is a required context. No contradiction exists, but the description adds little behavioral context beyond the structured annotations.

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 and front-loaded, which is good for conciseness. However, it is so brief that it borders on under-specification rather than effective conciseness. No waste exists, but a bit more explanatory content would make it more useful.

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 the tool has 8 parameters, a required company context, connection reference semantics, and no output schema, a one-sentence description is insufficient. The agent is left to infer that the result is a list, what fields it returns, how to handle pagination, and the connection lifecycle. This level of detail would be acceptable only for a trivial tool, which this is not.

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 schema covers 50% of parameters with descriptions (mainly companyName and connectionRef), while other parameters arise clearly documented. The overall description adds no parameter semantics and doesn't mention required companyName, the meaning of 'BRC', or connector behavior. This leaves the agent with incomplete guidance for filling in the non-descriptive parameters like pagination.

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 uses a specific verb ('Lists') and resource ('BRC bank accounts'), clearly identifying the tool's function as a read/list operation. The resource name distinguishes it from singular retrieval (brc_get_bank_account) and mutation tools (brc_create_bank_account, brc_update_bank_account). It does not further elaborate on scope or filtering, but the core purpose is unambiguous.

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 offers no guidance on when to use this tool versus alternatives like brc_get_bank_account, brc_list_accounts, or the batch variants. There is no mention of company context requirements, pagination behavior, or conditions under which this tool should be selected. The agent must infer usage entirely from the name and schema.

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