execute_spot

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

With no annotations, the description carries the full behavioral burden. It discloses the notable auth requirement (private key) and that execution is direct/irreversible, but omits slippage, the market-vs-limit default, builder-fee behavior, failure/partial-fill handling, and rate limits for a live financial mutation.

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?

A single front-loaded sentence with zero padding and the venue plus key requirement stated up front. It is efficient, though arguably too terse for an 8-parameter financial execution tool.

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?

For a live spot-order execution with 8 parameters, no annotations, and no output schema, the description is materially incomplete: it never explains the market/limit distinction, fee parameters, or expected outcome. An agent cannot confidently call it correctly from this definition alone.

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 only 63%, and the description mentions just the private key, adding nothing about coin, size, isBuy, price, or the undocumented isMarket default (true), builderFeeRate, and builderFeeAddress. It does not compensate for the schema's gaps.

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?

States a specific verb (execute), resource (spot trade), venue (HyperLiquid) and a distinguishing detail (private key). The word 'spot' separates it from the many perp siblings, but it does not clearly distinguish itself from buy_token/sell_token or limit_buy/limit_sell, which are also spot-order paths.

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?

There is no when-to-use guidance and no alternatives named, even though buy_token, sell_token, limit_buy, and limit_sell are obvious overlapping siblings. The agent must guess whether this is the canonical spot entry point or a lower-level fallback.

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