Is this edge deployable? Deflated Sharpe with a calibrated multiple-testing threshold (PAID $2.00)

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

Annotations already declare it is a non-read-only, open-world, non-idempotent, non-destructive call, so the safety profile is partly covered. The description adds genuinely new financial context not in the annotations: it is a paid call at 2.00 USD via x402 on base/usdc, plus the remote POST route. It still omits whether it is stateful, how the verdict is returned, or any rate/error behavior, so a mid score.

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 filler prose, and the paid-call caveat is front-loaded. However the first line is a verbatim repeat of the title, so roughly half the text adds no new information to an agent already shown the title.

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?

An output schema exists, so return values need not be spelled out, but the input side is completely opaque and the tool is a paid, non-idempotent call. For an agent to spend $2.00 correctly it needs to know what a valid 'returns' array looks like and how trials/claimed_sharpe interact — none of which is present.

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 0% across 6 parameters, so the description carries the full burden and supplies essentially nothing: no explanation of 'returns' (per-period vs daily vs monthly), 'trials' (number of configurations tested for the deflation), 'claimed_sharpe' (optional self-report?), 'benchmark_returns', 'as_of', or 'periods_per_year' default 252. The mention of Sharpe/threshold only weakly hints at which parameters matter.

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?

The description names a specific statistical operation (deflated Sharpe ratio against a calibrated multiple-testing threshold) and frames its purpose as deciding whether a strategy edge is deployable. That is more specific than a tautology, but there is no verb+resource phrasing and no statement of what the call actually consumes (a return series) or returns, so an agent must still infer the mechanics from the name and params.

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?

No guidance on when to use this versus adjacent siblings such as v1_quant_significance, v1_edge_replication, v1_strategy_capacity or v1_quant_monte_carlo, which plausibly overlap. The only usage-adjacent information is the price and payment route, not a selection criterion.

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