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

With no annotations, the description carries the full burden, and it does disclose useful traits: it is free, it is a lookup (non-mutating by nature), and it returns a bounded top 3 with specific fields — which partially substitutes for the missing output schema. It does not say whether data is live, how matches are ranked, or what happens when no name matches.

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, front-loaded sentences: the cost hook ('FREE') and the core question lead, then the result shape. The arrow shorthand is slightly cryptic but still parses in one read.

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 one-parameter lookup with no annotations and no output schema, the description covers the return shape well, which is the main gap it needed to close. It falls short on name formatting and on routing versus bank_profile, both of which an agent needs before choosing this tool.

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 single 'name' parameter has 0% schema description coverage, so the description must compensate. 'Name search' usefully implies the parameter is the bank's name rather than an ID, but it gives no guidance on format — legal name vs. partial string, abbreviations, or how broad matches are matched.

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 question it answers (is this US bank FDIC-insured and active) and the mechanism (name search returning top 3 with assets, deposits, location). This is clear enough to act on, but it never distinguishes itself from the sibling bank_profile, which plausibly answers overlapping questions.

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 when-to-use or when-not-to-use guidance, and no mention of the sibling bank_profile that likely competes for the same lookup intent. Only an implicit cue ('Name search') suggests you need a bank name to call it.

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