get_hl_meta_and_asset_ctxs

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

With no annotations provided, the description carries the full burden; it does disclose the useful behavioral fact that no authentication is required. However, it says nothing about rate limits, response size, caching, or whether the data is a live snapshot versus a static reference — all relevant for a market-data fetch.

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?

A single compact sentence with the resource front-loaded and the auth constraint appended; every clause carries information and there is no padding.

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?

There is no output schema and no annotations, so the description should convey what comes back — particularly what 'asset contexts' means and in what shape. It covers purpose and auth but leaves the return payload entirely unspecified, which is a real gap for a data-fetch 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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter surface the description needs to explain.

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 (Get) and resource (market metadata and asset contexts) plus the source system (HyperLiquid). It does not differentiate itself from close siblings such as get_hl_all_assets, get_all_mid_prices, or get_hl_perp_dexes, which also return HyperLiquid market data.

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?

The description gives no when-to-use guidance and names no alternative tool. The 'No auth' note implies it is callable without credentials but does not say when an agent should prefer this over the other HyperLiquid market-data endpoints.

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