Live price, volume and open interest for markets

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the concrete return payload (mark/oracle/mid price, volume, OI in coins and USD) and notes that the top-markets list additionally includes max leverage. No rate-limit or pagination context, but for a read-only snapshot tool this is solid added value.

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?

Four short sentences, front-loaded with the returned data then the usage rule and the edge-case market type. No filler or restatement of the title.

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 only two optional parameters, full schema coverage, and no output schema, the description carries the return-value burden itself and does so explicitly (fields plus units plus the leverage extra). Nothing an agent needs to call it correctly is missing.

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 the schema already documents both 'top' (default 15, max 100) and 'coins' (max 20). The description adds only the HIP-3 naming convention ("xyz:TSLA"), which the schema's own example already shows, so it sits at the baseline.

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 verb-less but precise operation: returns current mark/oracle/mid price, 24h volume and open interest for one or more markets. The word 'Current' implicitly separates it from hydromancer_price_history and hydromancer_open_interest_history, but no sibling is named explicitly.

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?

'Leave coins empty for the top markets by 24h volume' gives clear invocation guidance for the default path, and the HIP-3 note tells the agent which market universe is supported. No explicit when-not or named alternative (e.g. use price_history for time series) is offered.

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