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

With no annotations, the description must disclose behavioral traits. It only states what resource is returned, but does not mention idempotency, data freshness, pagination, or any side effects. For a tool requiring no parameters, the behavior is simple, but there is no explicit confirmation that it is a safe read operation.

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?

One extremely concise sentence that immediately states the tool's purpose. It is appropriately front-loaded with the key concept 'Tradeable'. Could be slightly more descriptive, but for a param-less tool this is sufficient.

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?

Given no output schema, the description should at least hint at what the returned universe looks like (e.g., list of asset symbols or objects). It only says 'Tradeable asset universe' which is vague. While the intended use may be clear from context, it lacks explicit completeness regarding output format.

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?

Zero parameters and 100% schema coverage, so baseline 3 is appropriate. The description adds no parameter meaning beyond what the schema provides, but no additional info is needed.

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?

The description explicitly states 'Tradeable asset universe (Hyperliquid xyz DEX)', clearly identifying that this tool returns the list of tradeable assets on the Hyperliquid DEX. No tautology; it distinguishes from siblings like 'candles' or 'calendar' which serve different purposes.

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?

No guidance on when to use this tool vs. alternatives. It does not mention that this should be called before querying other data tools that require an asset identifier, nor does it explain any prerequisites. The agent is left to infer usage context.

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