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

No annotations are provided, so the description carries the full burden, and it does disclose real behavioral context: it is a paid GET endpoint ($0.1 via x402), read-oriented, and enumerates what the payload contains including the half-Kelly sizing hint and model-labeling risk notes. It omits things like freshness/caching or latency, keeping it short of a 5.

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?

Front-loaded with the core purpose, then the enumerated payload, then the slug-source pointer, with endpoint metadata quarantined in a bracketed trailer. Dense but every clause earns its place; only the metadata bracket is slightly noisy.

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?

There is no output schema, so the description must describe returns and it does so adequately (probability, distribution, divergence history, sizing, risk notes). Combined with the slug-source routing and endpoint/pricing metadata, an agent has enough to call it correctly, though freshness and error behavior remain unspecified.

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% and the single slug parameter has only a regex pattern in the schema. The description compensates by directing the agent to /v1/edge/weather-markets as the source of valid slug values, giving meaningful semantic guidance beyond the schema.

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+resource: a deep model-vs-market breakdown for a single weather market, enumerating the concrete outputs (model probability with discretized distribution, divergence history, half-Kelly sizing hint, risk notes). This clearly distinguishes it from sibling edge_weather-markets, which lists markets rather than detailing one.

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?

Explicitly routes the agent to edge_weather-markets ('Find slugs via /v1/edge/weather-markets') to obtain the required slug, which clarifies the workflow relative to that sibling. It does not state when NOT to use it (e.g. vs edge_weather-markets-delayed), so it stops short of a 5.

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