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

With no annotations, the description carries the full burden and does useful work: it exposes freshness fields to check, warns that OFI is not candle-close synchronized, and clarifies that |OFI| >= 0.30 is interpretive context rather than an entry gate or exit/re-entry signal. It omits auth, caching, or rate-limit behavior, but the interpretive caveats are genuinely valuable and not derivable from structured fields.

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 lines are front-loaded with what the snapshot contains, then the freshness check, then the OFI interpretation caveat — each sentence earns its place. Density of jargon slightly reduces readability, but there is no filler.

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. For a zero-parameter snapshot tool the description covers the essentials: what is returned, how to judge staleness, and how to interpret the OFI figure. Only cross-tool routing guidance is missing.

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; the baseline for a no-parameter tool applies. The schema requires no additional explanation.

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 resource (the latest Confluence Tape snapshot) and enumerates its contents (rolling ofi_5m, tape_5m, quadrant), so an agent knows what it retrieves. It offers no differentiation from siblings like get_cvd_liquidity or get_gex_profile, and the domain jargon ('tape', 'quadrant') may not be self-explanatory.

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?

It gives a concrete operational instruction — verify ts/updated_at, age_sec and stale before trusting the data after a closed candle — which implies when the snapshot is usable. It does not state when to prefer this tool over sibling market-data tools or name an alternative, leaving selection to inference.

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