hl_meta

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the metadata contains (universe, decimals) but does not explicitly indicate that it is a read-only operation, nor does it describe any side effects, auth requirements, or output behavior beyond the schema.

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?

The description is extremely brief, which is concise, but it is a fragment rather than a well-formed sentence. It lacks structure and reads more like a terse annotation, sacrificing clarity for brevity.

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 the simple tool (1 optional parameter, output schema present), the description gives a basic idea but fails to explain how to invoke it correctly. The parameter is undocumented, and no usage context is provided, making it inadequate for an agent to select and call the tool reliably.

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 only parameter 'dex' has 0% schema coverage, and the description does not mention it at all. The agent has no information about what 'dex' means, what values it accepts, or whether it is required (though the schema shows it has a default and is not required).

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 clearly identifies the resource as perp metadata and specifies its content (universe, size decimals), distinguishing it from sibling tools like hl_spot_meta. However, it lacks an explicit verb such as 'get' or 'fetch', which leaves the action slightly implicit.

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 provides no guidance on when to use this tool versus alternatives like hl_meta_and_asset_ctxs or hl_spot_meta, nor does it mention any prerequisites, exclusions, or context for use.

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