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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add genuine context the annotations can't convey: the two upstream data sources and the units convention ($000s for dollar amounts, percentages for ratios), which matters for interpreting returned values. It still omits return shape, pagination defaults, and how the two sources are reconciled (duplicates, coverage gaps).

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?

Two short sentences with no filler, and the data-source identification is front-loaded ahead of the units note. It is efficient, though the terseness comes at the cost of leaving core scoping behavior unstated rather than because anything extraneous was trimmed.

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?

With six parameters, one required, no output schema, and four sibling branch tools to disambiguate against, the definition does too little. An agent cannot tell from the description that results are scoped to a single institution via rssd_id, what a row contains, or how the FDIC and NIC records combine — all of which the schema alone does not answer.

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 100%, so every parameter including rssd_id, q, state, sod_year, limit, and offset is already documented in the schema, setting the baseline at 3. The description adds nothing parameter-specific; the units note is about output values, not inputs.

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 names the resource (branches) and both upstream sources (FDIC Summary of Deposits and Fed NIC org-structure), which tells an agent what data comes back. But it never states the action or scope — nothing says this returns the branch network for a given rssd_id — and it doesn't distinguish itself from siblings like bank_branches_fdic, bank_branches_nic, or bank_branch_map beyond implying it merges the two sources.

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?

There is no when-to-use guidance at all: no statement of when to pick this over the FDIC-only or NIC-only sibling tools, and no mention that rssd_id is required to scope the query. The only usage-adjacent content is a note on units, which is interpretive rather than routing information.

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