fdic_financials

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

Annotations already include readOnlyHint=true, so safety is covered. The description adds valuable context beyond that: data frequency (quarterly), unit of measurement (thousands), and the specific financial fields included. This is meaningful behavioral disclosure.

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 concise sentences with no waste. The first sentence states the main purpose and data source; the second adds filtering options and units. Front-loaded and easy to scan.

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 read-only filtered data tool with a well-documented schema, the description covers the essential aspects: data type, included fields, filtering, and units. It does not describe pagination or defaults, but those are available in the schema, and no output schema exists to explain return values.

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 parameters are already explained in the schema. The description repeats the filtering concept (CERT or STALP) but does not add new meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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?

Description clearly states it retrieves quarterly Call Report financial data for FDIC-insured banks, listing specific data points (assets, deposits, net income, ROA, ROE, loan loss reserves). This distinguishes it from sibling tools like fdic_history or fdic_failures, which focus on other aspects.

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?

Provides clear usage context by explaining the data source (quarterly Call Reports), included metrics, and how to filter by CERT number or STALP. It does not explicitly name alternatives or exclusions, but the context is sufficient for selecting this tool.

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