get_hip3_l4_orderbook_history

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that tool returns periodic full order-level snapshots and notes case sensitivity. Does not contradict 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?

Two concise sentences front-loading key information: purpose, tier, case sensitivity, and return type. No unnecessary words or repetition.

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?

Given full schema coverage, annotations covering safety, and presence of an output schema, the description is complete enough for a read-only historical query tool. Mentions the Pro+ tier requirement and case sensitivity, which are critical for correct invocation.

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?

Input schema has 100% description coverage for all 5 parameters. Description adds no additional parameter information beyond what schema provides, so baseline score of 3 is appropriate.

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?

Clearly states the tool retrieves HIP-3 L4 orderbook checkpoints, specifies it's Pro+ tier, and mentions case sensitivity. Distinguishes from siblings like get_hip3_l4_orderbook (current snapshot) and get_hip3_l4_diffs (diffs) by emphasizing historical snapshots.

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?

Indicates usage for historical orderbook snapshots, implying not for real-time current book (use get_hip3_l4_orderbook). Mentions Pro+ tier and provides example symbol. Could be more explicit about when not to use, but adequate for basic guidance.

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