reverse_engineer_winners

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

The description asserts 'Read-only', while annotations declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true — a direct contradiction about the safety profile. No other behavior is disclosed (cost, latency, rate limits, what a destructive side effect would even be), so the agent is left with conflicting signals.

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?

It is a single compact sentence rather than a wall of text, but it is overloaded with em-dash-separated jargon clauses and the safety claim is buried mid-string. Front-loading what the tool returns and the actual read/write behavior would be far more useful than the list of analysis names.

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?

With no output schema, the description should explain the shape of the returned scorecards, but it only names categories. Combined with zero annotations consistency and undefined domain terms ('board survivors', 'universe'), an agent cannot confidently predict inputs-to-outputs or cost for this analysis tool.

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%, so both 'max' and 'watchlist' are already documented, including the 'bypass board filters' behavior. The description restates the watchlist purpose ('force into the universe') without adding format, limits, or interaction details beyond the schema, so the 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?

Names a specific verb+resource ('reverse-engineer ... on-chain HyperLiquid wallets') and enumerates the outputs (skill-vs-luck scorecards, hold-time/leverage/sizing asymmetry, aggregate edges), which distinguishes it from neighbors like get_wallet_performance and get_hl_top_traders. The jargon ('prevalence-gated aggregate edges', 'the universe', 'board survivors') blurs exactly what analysis is produced.

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 guidance on when to choose this over the many wallet-analysis siblings (get_wallet_performance, get_hl_top_traders, get_hl_top_traders_by_pnl, get_wallet_info). The only conditional statement concerns the watchlist, not tool selection, and no exclusions or prerequisites are given.

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