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

No annotations are provided, so the description carries the burden. 'Lookup' and 'FDIC-insured' do imply a read-only registry query, and the returned-field list is useful. But it says nothing about result caps (limit defaults to 10), what active=true/false filters, or whether results are paginated — meaningful behavioral gaps for a list tool with zero annotation coverage.

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 sentences, front-loaded with the entity and filters, then the payload, then the use case. No filler. The long comma-separated field enumeration is dense but earns its place by telling the agent what data comes back.

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?

An output schema exists, so return-shape explanation isn't needed. The description covers the entity, filters, and payload well, but for a 5-parameter tool with no annotations and no schema descriptions, the unexplained limit/active semantics and absent result-size guidance leave gaps.

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 coverage is 0%, so the description must compensate. It does clarify that cert means 'FDIC certificate' and that name/state are free-form filters, which is real added value. However, limit (default 10) and active (default true) are never explained, leaving two of five parameters semantically opaque.

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 resource (FDIC-insured US banks) and the three filter axes (name, state, FDIC certificate) plus the returned fields, so an agent immediately knows what this returns. It does not name or differentiate against any sibling (e.g. us_company_profile, us_company_search), but no sibling covers FDIC bank data, so the ambiguity risk is low.

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?

'Use for bank research or counterparty checks' gives an implied usage context but no when-not conditions, no prerequisites, and no alternatives to consider. Adequate but leaves the agent to infer the boundary between this and the company-lookup siblings.

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