market_price

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

No annotations are provided, so the description fully shoulders the behavioral disclosure burden. It fails to mention any traits like permissions, rate limits, or response format details beyond mentioning 'current mark price'. The parameter useToonFormat implies a compact format but is not explained.

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 sentences, no unnecessary words. First sentence states purpose, second provides symbol format guidance. Efficient and well-structured.

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 should explain returned data format. It mentions 'compact toon format' implicitly via parameter but does not elaborate. The description is adequate for a simple price check but could be more complete.

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 baseline is 3. Description adds value for the symbol parameter by giving examples, but does not mention the useToonFormat parameter or its effect, leaving it to the schema alone.

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?

Description clearly states 'Get current mark price for any trading pair on Hyperliquid', specifying verb and resource. It also provides distinct symbol formats, distinguishing it from sibling tools like list_asset or market_orderbook.

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?

Description includes explicit guidance on symbol formats with examples (standard and builder dex). However, it does not mention when to prefer this tool over siblings like market_orderbook for depth data.

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