get_hl_user_stats

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

With no annotations, the description carries the full burden and does disclose two genuinely useful traits: no auth is required and results are cached for 1 hour (implying up to 1h staleness). It says nothing about rate limits, error behavior, or pagination, so it is helpful but not thorough.

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 terse sentences with zero filler; the metric list and the auth/caching facts are front-loaded and each clause earns its place.

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, but the description enumerates the main returned metrics, and the auth/caching facts cover the operational context for a simple read tool. Only the absence of any output-shape detail (e.g. per-day granularity) keeps it from a 5.

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 description coverage is 100% and the single userAddress param is already documented in the schema (including the managed-vs-control wallet distinction), so the description adds no parameter meaning beyond it. Baseline 3 applies.

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?

Specific verb (Get) plus resource (HL user trading stats) with the returned metrics enumerated (daily PnL, volumes, trade counts, win rates), which makes it recognizable against siblings like get_wallet_performance or get_trader_leverage. It stops short of explicitly naming a sibling it is not, so it misses the top tier.

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 states 'No auth' and 'Cached 1 hr' but gives no when-to-use or when-not guidance and does not point to any alternative among the many stats/performance siblings. An agent gets no routing signal beyond the tool's own scope.

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