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

With no annotations, the description carries the full burden. It discloses the output (ranked mispricings, probabilities, edge) and implies a read-only scan, but it does not explicitly state that no trades are placed or mention any side effects, limitations, or safety characteristics.

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?

The description is a single run-on sentence packed with specific tickers, model names, and jargon. It is not front-loaded or structured; it would benefit from splitting into a purpose statement and a details section. Every word does not earn its place.

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 tool has an output schema (true), so the description needn't detail return structures, yet it does summarize the key outputs (mispricings, probabilities, edge). The single optional parameter is not explained, but the core behavior and expected result are clear enough for a basic call.

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%, so the description must explain the target_date parameter. It does not mention it at all. The agent is left to infer that target_date is an optional date filter, but the description provides zero guidance on its format, meaning, or effect.

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 clearly states the verb 'Scan' and the resource: live temperature and weather prediction markets, listing specific tickers and models. It distinguishes itself from siblings like foresea_scan_markets (generic) and foresea_weather_forecast (likely just forecasting) by specifying the comparative mispricing analysis.

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 implies usage for finding mispricings in weather markets but does not explicitly state when to use this tool versus alternatives or provide exclusions. No contrast with sibling tools is given, leaving the decision to inference.

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