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

Annotations already establish the safe-read profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's job is to add context, and it does: the data source (Call Report), the freshness contract ('latest', plus reporting period and source returned), and the guarantee that units are stated on every value. That unit guarantee is genuinely useful for an agent doing downstream arithmetic on ratios. It does not say what happens for an unknown certificate, so the behavioral picture is not complete.

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?

One sentence, front-loaded with what the tool returns, then the field inventory, then the provenance and units caveat. Nothing is redundant. The long field list is dense but each item earns its place by telling the agent what metrics are available without an output schema.

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 single-parameter read tool with no output schema, the description compensates well by listing returned fields, the reporting period, the source, and the units convention. Missing pieces are edge behavior on an invalid certificate and whether data can be stale or restated, which matter modestly here. Overall the agent has enough to call it correctly and interpret results.

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 100% and the single parameter is documented with both its meaning (FDIC certificate number) and its provenance (from search_banks). The description adds no further meaning beyond that — no format hints, no notes on certificate reuse across charters or mergers. Baseline 3 applies when the schema carries this dimension.

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 (headline profile for one bank) and enumerates the exact contents: identity, total assets, deposits, loans, ROA, ROE, net interest margin, capital, liquidity and credit ratios. That makes it easy to distinguish from the sibling scenario tools (nim_rate_shock, maturity_wall_refinancing, etc.), which model hypotheticals rather than report raw Call Report figures. It stops short of explicitly naming those alternatives, so sibling differentiation is implied rather than stated.

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?

Usage is only implied: the word 'headline' and 'latest Call Report data' suggest a quick single-bank snapshot, and the certificate parameter's schema note points back to search_banks as the lookup step. There is no explicit statement of when to prefer this over the scenario/analysis siblings, nor any exclusion such as limits on historical periods. An agent can infer the use case but receives no routing guidance.

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