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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is lower. The description adds genuinely new behavioral context: output is "compact" (summarised, not full detail), "details stay on REST" (a scope ceiling), "cited" (provenance is included), and an explicit "display-only, never an institution score or investment advice" framing constraint.

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 verb and resource, then the caveats. Nothing is redundant, though the middle clause chain ("Undertow run-risk cross-read and compound flags") is dense internal jargon that costs a little parse time, and the display-only disclaimer, while worthwhile, is appended rather than integrated.

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 zero-parameter, annotation-covered read with no output schema, the description does the full remaining job: it names the record's fields, states that the payload is cited and compact, and caps expectations by pointing to REST for detail. An agent can call this and set user expectations without any further information.

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 zero parameters, so there is nothing for the description to disambiguate and the schema is trivially covered. Baseline 4 applies; the only concession is that the description does not say the call is argument-free or how the register is scoped (all institutions vs. a default slice).

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 verb plus a concrete resource ("Read the compact cited bank/crypto exposure register") and enumerates its contents: disclosed quantum, stablecoin/venue links, exposure channels, run-risk cross-read, compound flags. That distinguishes it in substance from siblings like crypto_regime_board or stablecoin_rails_board, but the description never names those siblings explicitly, so the agent still has to infer the boundary.

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: "Read the compact ... register" and "Details stay on REST" tell the agent this is a summary view with depth elsewhere, but it never says when to pick this over crypto_regime_board, stablecoin_rails_board, or failure_radar_board. No prerequisites or exclusions are given, so selection among near-neighbour boards rests on the content list alone.

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