pulse_global_stats

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

No annotations provided, so description carries burden. It explains what data is returned (traders, trades, volume, PnL, coverage period) and implies a read-only operation. No side effects or restrictions mentioned, but sufficient for a simple data retrieval tool.

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: first states purpose and data points, second gives usage guidance. No redundant words, highly efficient.

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 low complexity (one optional boolean parameter, no output schema), the description is complete. It lists all returned data points and provides usage guidance, meeting the needs for correct invocation.

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% with one parameter fully described. The description does not add extra semantics beyond the schema's description of 'useToonFormat'. Baseline 3 as schema does the heavy lifting.

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 it gets global Hyperliquid trading statistics and lists specific data points (total traders, trades, volume, PnL, data coverage period). It distinguishes from sibling tools which focus on specific assets or cohorts, making the global scope clear.

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?

Directly says 'Use this to understand the overall scale of the market', providing clear context. However, it does not explicitly exclude cases or mention sibling alternatives, though the purpose implicitly sets it apart.

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