Are these two strategies the same bet? Signed correlation matrix and clusters (PAID $0.10)

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

Annotations already declare openWorldHint=true and readOnlyHint=false, and the description usefully adds the concrete cost and payment rail (0.10 USD via x402 on eip155:8453) plus the POST route, which is real behavioral context. However it says nothing about what happens on insufficient payment, size/length limits on return series, or minimum observations required for a correlation, and readOnlyHint=false on a pure compute call is unexplained.

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 lines, zero padding, and the route/payment detail is cleanly separated. But the brevity comes from echoing the title rather than from disciplined editing, so it is under-specified rather than concise.

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 explained, and the price/rail is covered. What remains missing for a paid, open-world compute endpoint is significant: no parameter meaning, no input-shape constraints (how long must each returns series be, how many strategies are supported), and no payment failure behavior.

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% for the three top-level parameters, so the description carries the burden and adds nothing: 'as_of', 'threshold' (default 0.7), and 'strategies' are never mentioned. Only the nested schema's own note on the strategy object hints at semantics, and that is structured data, not description content.

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 communicates the resource (signed correlation matrix and clusters) but does so by restating the title verbatim, adding no new framing beyond the route line. The framing 'Are these two strategies the same bet?' also conflicts with the schema, which takes an array of N strategies rather than a pair, so an agent may misjudge the input shape.

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 at all: no statement of what question this answers relative to siblings like v1_quant_significance, v1_portfolio_risk, or v1_strategy_capacity, and no prerequisites. The only editorial signal is the price, which does not tell the agent when this tool is the right choice.

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