live_coin_risk_snapshot

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

No annotations provided; description reveals return fields (OI, wallet count, L/S posture, etc.) implying a read-only operation with no side effects. Could explicitly state it's non-destructive, but the listed outputs strongly suggest a snapshot view.

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 efficient sentences: first delivers core purpose, second provides usage triggers and return summary. No wasted words, front-loaded.

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?

For a simple read tool with 2 parameters and no output schema, the description adequately covers purpose, usage context, and return fields. Might omit notes on rate limits or authentication, but not critical for this 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 description coverage is 100%, so parameter meanings are already fully documented. The description adds no extra detail beyond what the schema provides for either 'coin' or 'useToonFormat'. Baseline score of 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?

Clear verb+resource (Get risk snapshot) for a single coin. Distinguishes from siblings like live_coin_risk_history and live_risk_overview by specifying 'single coin' and 'current snapshot'.

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?

Explicitly lists example questions ('is BTC crowded?', etc.) that trigger usage, providing clear when-to-use guidance without needing to reference alternatives.

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