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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the baseline is low. The description adds real value beyond that: it discloses provenance/audit content (PIT source/rights, six venue clocks, startup SHA) and reiterates the live-mode exclusion, telling the agent this is a frozen, license-aware snapshot rather than a live check.

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?

Dense but compact: the scope is front-loaded and the exclusion closes the sentence with no wasted filler. The fragment-list style occasionally hurts readability, but the size is appropriate for a low-complexity read tool.

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 enumeration of hash/PIT/rights/conversion/clock/SHA effectively doubles as a return-value summary, which is helpful. Yet the null-typed venue parameter and the exact meaning of "clearance" are never resolved, leaving gaps for a 6-required-param tool.

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 coverage is only 33%, so the description should compensate more than it does. It reinforces the request-hash and exact-rung semantics that the schema already documents, but says nothing about mode, side, instrument, or the puzzling null-typed venue parameter, which the schema leaves 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?

Names a scope ("exact-rung BTC/USD observe/paper") and enumerates the context elements produced (request hash, PIT source/rights, conversion, bid bands, venue clocks, startup SHA), so the agent can tell roughly what it returns. However "exit context" is jargon and the phrasing is telegraphic, so the actual verb/action is never plainly stated. It does not distinguish itself from siblings like crypto_exit_check or exit_cost.

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?

"No live mode/clearance" provides an explicit when-not constraint, and the observe/paper scope implies when it applies. But no named alternative (crypto_exit_check, exit_cost, unwind_watch) or positive selection criteria are given, so the agent must infer which exit-related sibling to choose.

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