pulse_recent_trades

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

No annotations provided; description covers sorting behavior and real-time scope. Lacks details on edge cases (e.g., empty results) or limitations, but adequate for simple 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?

Two sentences, no redundant information. Front-loaded with key action and result. Every word serves a purpose.

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 or annotations, description explains sorting, purpose, and timeframe. Could mention response format or pagination, but covers essential context for tool usage.

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%; description adds minimal extra meaning beyond the schema. Implies timeframe via 'last N minutes/hours' but does not enrich parameter understanding significantly.

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?

Clearly states verb 'Get', resource 'biggest trades on Hyperliquid', and specifics like sorting by absolute PnL and timeframe. Differentiates from siblings by focusing on 'biggest trades' and real-time activity.

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?

Explicitly suggests usage context: 'Use this to see what's happening right now on the exchange.' Does not provide when-not-to-use or alternatives, but context is sufficient for basic guidance.

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