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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false. The description adds meaningful behavior beyond that: it is 'display-only,' 'never an institution score or investment advice,' and returns only compact/cited data, with detailed disclosures intentionally left to the REST detail route. No contradictions with annotations.

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 description is compact and front-loaded with the core action and resource, followed by a useful pointer to the detail route and a caveat. Every sentence adds value, though the dense cluster of domain jargon ('Undertow run-risk cross-read and compound flags') makes it slightly less immediately digestible.

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 no-argument, read-only board, the description covers what the tool returns, its compact nature, and where fuller details live. There is no output schema, so the enumerated content fields help close that gap. It does not describe the exact response format, but this is a low-complexity display tool and the caveats plus annotations provide adequate context.

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 has zero parameters and the input schema already documents this fully (empty properties, additionalProperties=false). The description redundantly notes 'Takes no arguments,' which is harmless, and there are no parameter semantics left unexplained.

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 and resource: 'read the compact cited bank/crypto exposure register,' and enumerates the register's contents (quantum, stablecoin and venue links, exposure channels, Undertow run-risk cross-read, compound flags). It is clearly a read-only board tool, but it does not explicitly contrast itself with closely related siblings like crypto_regime_board or stablecoin_rails_board.

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?

The description implies when to use the tool: for the compact register, while 'detailed disclosures stay on the public REST detail route' signals where to go for more depth. It does not discuss sibling alternatives or give explicit when-to-use/when-not-to-use guidance relative to other boards.

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