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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds value by stating what it does NOT do ('No live mode or clearance'), but gives no rate-limit, auth, or freshness/pagination behavior for a read that is clearly state-sensitive (PIT, startup SHA).

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?

A single dense sentence that front-loads the scope ('Exact-rung BTC/USD observe/paper') and then the payload. It is efficient, though the acronym stacking costs readability without adding routed meaning.

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 read-only tool with no output schema, listing the returned artifacts (request hash, bid bands, venue clocks, SHA) is genuinely useful completeness. But it omits any parameter semantics for six required params and offers no alternative-tool routing, leaving gaps an agent must fill from the schema alone.

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% and the description's list (bid bands, venue clocks, startup SHA) reads as outputs, not parameters. Only 'observe/paper' and 'exact-rung' loosely map to the mode and requested_size_usd enums, leaving side, venue, and instrument explained solely by their const values.

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?

It conveys that this returns observe/paper exit context for an exact BTC/USD rung and enumerates the returned artifacts (request hash, clocks, SHA). However, the verb is implicit and the jargon ('PIT-bound', 'exact-rung') plus the vague noun 'context' make the actual action less than crisp, and no sibling (e.g. crypto_exit_check, exit_cost) is named to disambiguate.

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 or clearance' combined with the mode enum [observe, paper] implies this is only for observe/paper simulation, giving an implicit boundary. But it never states when to choose this over crypto_exit_check or exit_cost, so the routing guidance is left to inference.

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