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

With no annotations, the description must carry behavioral burden. It signals cost ('FREE'), implies read-only via 'List', and discloses the return fields, which is useful given no output schema. But the remaining sentences ('Information only, not betting advice. Historical settlements do not predict future results. 18+. BeGambleAware.org') are compliance boilerplate that adds no operational context — nothing about pagination beyond the schema's limit, coverage of cities, or rate limits.

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 purpose and the settlements handoff are correctly front-loaded in the first two sentences. However, roughly a third of the text is a trailing gambling disclaimer that an agent gains nothing from and which dilutes an otherwise tight definition.

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?

For a 3-parameter, read-only listing tool with no output schema, the description covers what the tool is for, what it returns, and what to do with the result. What's missing is minor: whether results are global or fixed to a set of cities, and behavior when city/kind are omitted (all three params are optional).

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 coverage is 67%, and the description compensates where the schema is silent: it explains 'by city or keyword' for the city param and enumerates the four kinds (high/low/rain/snow) whose enum has no schema description. It adds nothing for limit, but the schema already covers that with 'default 25, max 100'.

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 and resource — 'List Kalshi weather series (daily high/low temperature, rain, snow)' — with the filtering axis (city or keyword) and the fields returned (ticker, frequency, settlement source). It also positions itself against the complementary sibling kalshi_weather_settlements, so an agent can tell the two apart without opening either schema.

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?

'Use the ticker with kalshi_weather_settlements' gives an explicit downstream handoff, which is genuine routing guidance. It does not state any when-not-to-use condition or name a competing discovery tool (market_lookup, search_markets), so it stops short of full when/when-not coverage.

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