get_lighter_l3_orderbook_history

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds value by detailing return content (order-level snapshots with IDs, addresses) and tier requirement (Pro+). Does not mention pagination or rate limits, but these are covered by schema 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 sentences, no wasted words. First sentence states action and tier, second describes return fields. Front-loaded with key decision factors (historical, L3, Pro+).

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?

Tool has 6 params and an output schema. Description covers purpose, return content, and tier. Could mention pagination cursor or depth parameter behavior, but output schema likely covers return structure. Nearly complete.

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 has 100% description coverage. Description's 'over a time range' loosely references start/end, but adds no structural meaning beyond schema. Baseline 3 as schema carries parameter info.

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?

Description clearly states 'Get historical Lighter L3 orderbook snapshots' – specific verb, resource, and scope. It distinguishes from real-time (get_lighter_l3_orderbook) and other levels (L2, L4) by specifying L3 and historical nature. Lists returned fields (order IDs, user addresses, prices, sizes) for precision.

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?

Implied context: historical snapshots vs. current data, and Pro+ tier restriction. But no explicit when-to-use or when-not-to-use compared to siblings like get_lighter_l3_orderbook (real-time) or get_lighter_orderbook_history (likely L2). Alternatives not named.

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