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

Goes beyond the safety annotations by disclosing the data source ('Kalshi public data only'), the staleness profile ('Refreshed about every 5 seconds'), and a non-obvious nullability rule ('null until Kalshi posts it'). It does not say what happens when no window is open or on partial failures, which keeps 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 market identity, followed by a dense field enumeration and two short qualifying sentences; no padding. The long middle clause is list-heavy and partly duplicates what the output schema already declares, but it remains readable and purposeful.

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?

With an output schema present, return values need not be explained, and the description still supplies the remaining context an agent needs: data provenance, freshness, no-signal disclaimer, and strike nullability. Adequate for a zero-parameter read tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning left to compensate for. The description correctly adds no parameter prose.

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?

Names a specific resource and scope: 'The Kalshi KXBTC15M Bitcoin up/down market trading now', plus the exact fields returned. The 'trading now' qualifier cleanly separates it from get_graded_record (settled markets) without needing the schema opened.

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?

Usage is implied rather than stated: 'trading now' suggests live-window lookups and the ~5 second refresh cadence implies polling, but no sibling is named and no explicit when-not condition is given. An agent can infer the context, yet get_graded_record vs this tool is never made explicit.

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