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

Annotations already cover the read-only and open-world profile, and the description adds real value beyond them: the data provenance (FDIC Failed Bank List) and the non-obvious display scaling where asset/deposit totals are in billions while costs and recent-failure rows are in millions. That scaling caveat is exactly the kind of behavior an agent needs to avoid misreporting numbers. It does not cover freshness/cadence of the underlying list.

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 tool's scope, then the units caveat. Every clause (totals, KPIs, series, rollups, source, both unit scales) carries distinct information. Slightly dense and telegraphic, but nothing is wasted.

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 has to convey the return shape, and it does so by listing the dashboard's component blocks plus the unit conventions for each. The only loose end is the 'acquisitions' half of the name, which is never described in the enumerated contents.

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 tool takes no parameters, so there is no parameter meaning to add; per the baseline for zero-parameter tools this scores 4. The description correctly implies the call is unfiltered and always returns the full composite view.

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?

Names a specific resource (composite failures-and-acquisitions dashboard) and enumerates its contents: all-time totals, period KPIs, failures-by-year series, by-state and by-resolution rollups. An agent can tell this is an aggregate view rather than a row-level query, though it never explicitly distinguishes itself from the granular siblings failures_by_year and failures_recent that it partially overlaps.

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?

Says nothing about when to choose this tool over failures_by_year, failures_recent, or industry_dashboard. The word 'composite' implies an overview use case, but no alternative is named, no exclusion is stated, and no prerequisite or follow-up guidance is given.

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