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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description still adds real operational context: the data is live mid price, the upstream venues differ by market, the value is in USD, and failure is null-safe ("returns price=null with a note if the symbol is not found") — the only gap is no note on staleness or rate limits.

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?

Front-loaded with purpose and query-matching triggers, then venue detail, then return shape — a sensible order. The middle sentence carries a long, example-stuffed parenthetical that is denser than needed, but nothing is redundant.

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 no output schema, the description does the work of specifying the return (numeric USD price, null plus note when unresolved) and covers both market paths and default behavior implied by the schema. It leaves out response timing/staleness guarantees, which is a minor omission for a live-quote 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 coverage is 100%, so the baseline is 3. The description goes slightly beyond by showing the ticker space for both markets (BTC/ETH/HYPE/SOL vs SMSN/SKHX/NVDA/AAPL/TSLA/GOLD) and clarifying that the crypto/equity enum selects which perp dex is queried, reinforcing how the two params interact.

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+resource ("Get the LIVE mid price for a ticker") and pins down the two market modes it spans — HyperLiquid's main perp dex and the builder-deployed equity dex. It never names or contrasts the obvious sibling get_price_stats, so an agent must infer the split from the return-shape hint ("numeric price") rather than from an explicit statement.

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?

Gives concrete when-to-use triggers via quoted user phrasings ("what's X trading at?", "price of X") and "any quote request", which maps cleanly onto intent routing. It offers no exclusions or alternatives, so the boundary against get_price_stats and search_tokens is left implicit.

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