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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds provenance ('public', 'compiled from FDIC') which is genuinely useful, but says nothing about data currency, coverage of branches versus institutions, pagination behavior of limit, or error behavior for unknown certs.

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 tight sentence with no filler or repetition. It is slightly back-loaded, though: leading with an action verb and the queryable identifiers would orient the agent faster than the provenance clause.

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 no output schema, the description carries the burden of telling the agent what a result contains, yet it only gestures at 'health and branch metrics' without naming any returned fields or record shape. For a three-parameter lookup tool with full annotation coverage, this is adequate but leaves a real gap about what comes back.

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 all three parameters (cert, name, limit) are already documented with examples and a default. The description adds no meaning beyond the schema, notably failing to state whether searching by cert and name simultaneously is supported or how they combine.

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 precisely: bank health and branch metrics sourced from FDIC. It is a noun phrase with no explicit verb (search/lookup/get) and never contrasts itself with entity-lookup siblings like gleif_lei_kyb or sec_edgar_cik_lookup, so an agent must infer that this is a retrieval tool and that its differentiator is the FDIC supervisory/branch dataset.

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 guidance on when to choose this over the many entity/bank-adjacent siblings, and no explanation of how cert and name relate (does one take precedence, may they be combined, what happens with zero required parameters). The regulatory citation is context, not usage guidance.

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