get_hip4_summary

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

Annotations already indicate read-only, idempotent, open-world. Description adds behavioral details: returns price, volume, OI aggregates, and clarifies mark_price is implied probability (0..1) not USD, which is important for correct interpretation. 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?

Two sentences front-load purpose and coin example, then clarify return fields and mark_price semantics. Every sentence adds value with zero waste.

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?

Output schema exists, so description need not detail return structure. It adequately names the key aggregates (price, volume, OI) and resolves ambiguity about mark_price. For a summary tool with good annotations, this is 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 coverage is 100% with a detailed description of the coin parameter. Description echoes the accepted forms but mainly adds context about the summary itself. With high schema coverage, baseline is 3; description adds some value but is largely redundant on parameter meaning.

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 the tool retrieves a combined HIP-4 24h market summary for a coin, with specific verb 'Get', resource 'HIP-4 summary', and scope '24h'. It distinguishes from sibling summary tools like get_hip3_summary by explicitly naming HIP-4.

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?

Description provides guidance on coin format (canonical vs legacy forms) and references get_hip4_instruments for listing coins. While it does not explicitly enumerate when to use vs alternatives, the context is clear for a high-level summary tool among many HIP-4 detail tools.

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