HTX Get Risk Snapshot

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

Annotations already disclose read-only/idempotent behavior; description adds that it supplies facts/warnings and does not make a trading decision, reinforcing the non-destructive nature without contradiction.

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 focused sentences: purpose first, behavioral limitation second. No redundant or irrelevant content.

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?

Combined with complete schema and annotations, the description gives enough context for a read-only snapshot tool. Pre-trade framing and the non-decision caveat cover key boundaries, while output details are left to the output schema.

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 covers all parameters with descriptions, enums, and defaults. Description adds no parameter-specific meaning beyond the overall pre-trade context.

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?

States a specific purpose: combine current market and account state into a pre-trade risk snapshot. Clearly distinguishes from decision/execution tools and from market/account snapshot siblings.

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?

Implies pre-trade use and non-execution, but does not explicitly state when to choose this over sibling snapshot, validation, or preview tools.

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