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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuine behavioral context beyond them: each section retains its own dates, units, rights and limitations; there is no combined score or trade authorization; and revision handling suppresses identical rows rather than evidence checks. It does not cover rate limits, pagination, or how the bounded cap behaves, but the added caveats are substantive.

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?

The purpose leads the description and the five short sentences are dense with specific constraints rather than filler. It is slightly jargon-heavy (Seiche, LiquiLens, Undertow are opaque without background), but nothing is redundant.

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 values need not be explained, and the annotations cover safety. The description does well on scope caveats (no combined score, per-section rights/units), but with three zero-coverage parameters it leaves the limit semantics and revision-hash expectations under-specified for an agent to invoke confidently.

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 0%, so the description carries the burden. It explains 'bank' well (literal name or ID, empty means published coverage) and gestures at previous_revision via the revisions sentence, but 'limit' is never defined and the 'bounded call' wording only indirectly implies it; the hash format expected by previous_revision is left to the schema pattern alone.

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 a specific verb (Review) and three concrete resources (dollar-funding benchmarks, covered-bank diagnostics, market liquidity) and frames the call as a combined, bounded retrieval. It is clear what the tool returns, though it never explicitly distinguishes itself from the closely named sibling financial_evidence_funding_review, so an agent must infer the split.

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 implied through the 'one bounded call' framing and the note that empty bank selects published coverage, which tells the agent when the filter is optional. However, it gives no when-not guidance and does not route the agent between this and the many sibling evidence tools (funding_review, query, datasets), leaving the alternative-selection decision to inference.

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