HTX Get Market Snapshot

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

The read-only, idempotent, and non-destructive behavior is already covered by annotations. The description adds useful behavioral context by noting that the snapshot is concurrently collected and compact, and it references optional raw envelope inclusion, which is transparent about output shape.

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?

The description is two sentences, front-loaded with the core purpose, and contains no redundant or vague wording. It efficiently communicates purpose, usage, and an alternative.

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?

With a full output schema and well-documented parameters, the description provides sufficient context for correct use. It clearly addresses the main decision point against sibling tools and explains the aggregate nature of the snapshot.

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?

The input schema covers all five parameters with descriptions and enums, so the baseline is 3. The tool description itself does not add much parameter-level meaning beyond the schema, though schema descriptions are already clear.

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 a specific verb and resource: 'Return one compact, concurrently collected market snapshot'. It also distinguishes this aggregate tool from low-level market calls and explicitly names a sibling tool, htx_get_technical_indicators, for technical analysis.

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 gives explicit usage guidance: prefer this aggregate over several low-level market calls, and use htx_get_technical_indicators instead when technical analysis is needed. This directly helps an agent choose between competing tools.

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