get_hip3_orderbook

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

Annotations already declare readOnly=true, idempotent=true, and non-destructive. Description adds value by noting case sensitivity, free-tier restriction, and return structure (bids, asks, mid price). No contradiction with 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?

Three concise sentences: purpose, case sensitivity/example, tier restrictions. No redundant information; every sentence adds critical context.

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 (not provided), description appropriately avoids duplicating return details. Covers purpose, parameter nuances, limitations, and references related tool for listing symbols. Adequate for a snapshot tool with robust annotations.

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 descriptions. Description enriches 'coin' parameter with examples, case sensitivity warning, and market count (125+ across 6 builders). 'depth' parameter is minimally enhanced but schema already describes it sufficiently.

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 the current HIP-3 orderbook snapshot' with specific verb and resource. Differentiates from siblings by emphasizing 'current snapshot' and mentioning specific symbol caveats like case sensitivity and free-tier limitation.

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?

Provides explicit usage guidance: free tier only supports 'km:US500', Build+ supports all HIP-3 symbols. Suggests using get_hip3_instruments to list symbols. Missing explicit when-not-to-use alternatives like history or L2-specific tools, but context is sufficient.

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