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

No annotations are present, so the description carries the full burden. It does disclose the analytical model and the kinds of outputs (mispricings, implied odds, calibration reliability, paper equity curves), which is useful. It omits safety profile, rate limits, pagination, and whether results are live vs cached, leaving meaningful behavioral gaps for a tool with no annotations.

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, front-loaded with the domain scope (which market, which contract) followed by the analytical approach. Efficient, though the return-value enumeration is partly redundant given an output schema exists.

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?

The output schema covers return values, yet the description still enumerates them while saying nothing about the two undocumented input parameters or usage context. For a 2-parameter, no-annotation tool the definition is serviceable but leaves clear gaps.

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?

Both parameters (limit, min_edge) have 0% schema description coverage, and the description adds no meaning for either — it never explains what limit caps or what units/threshold semantics min_edge uses, despite mentioning 'mispricings' conceptually. With low coverage the description was expected to compensate and does not.

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 (scan) and resource (Kalshi crypto prediction markets / KXBTCD threshold contracts) and names the scoring methodology (Black-Scholes zero-drift diffusion, spot volatility), which is more specific than most siblings. It does not, however, distinguish itself from near neighbors like foresea_edge_board or foresea_scan_markets, so an agent still has to guess which scan variant applies.

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?

The description says what the tool does but never says when to choose it over foresea_edge_board, foresea_scan_markets, or foresea_analyze_market. No preconditions, no exclusions, no alternative routing.

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