get_hip3_price_history

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

Annotations already declare readOnly, destructiveHint, idempotent. The description adds that it returns mark, oracle, mid prices and supports aggregation intervals, providing some behavioral context beyond annotations, but does not cover pagination or data retention.

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?

Three concise sentences front-loaded with purpose, case-sensitivity warning, return values, and interval support. No fluff 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 output schema exists, the description covers core functionality well. Could mention pagination (cursor) and clarify difference from get_hip3_candles, but still fairly complete for a price history 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 100% with detailed parameter descriptions (e.g., coin examples, start/end defaults, interval enum). The description adds minimal parameter-specific semantics (mentions case-sensitivity for coin but that's already in schema). Baseline 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?

The description clearly states 'Get mark/oracle/mid price history for a HIP-3 coin over a time range', specifying the verb (Get), resource (price history), scope (HIP-3 coin, time range), and return values (mark, oracle, mid price). It distinguishes from siblings like get_hip3_candles (OHLCV) by focusing on price types.

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?

The description implies usage for HIP-3 price history and notes case-sensitivity, but does not explicitly state when NOT to use it (e.g., for candles use get_hip3_candles). However, the context and sibling names make differentiation possible.

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