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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the data is public and comes from market-data JSON, which is useful context, but says nothing about freshness, caching, or failure behavior. Adequate but not rich given the lower bar set by 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 short sentences with no padding and the core purpose front-loaded. The trailing sentence is a bit redundant in phrasing ('retrieve kalshi exchange schedule' restates the sibling's name), but the description stays tight.

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?

A zero-argument read tool with annotations covering the safety profile and an output schema describing the return payload. The description covers what it returns and where the data comes from, leaving nothing critical missing for correct invocation.

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 per the rules the baseline is 4. There is no parameter behavior for the description to compensate for.

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 verb+resource (returns exchange and trading active flags) and identifies the data source (Kalshi market-data JSON). It contrasts itself with the closely-named sibling kalshi_exchange_schedule, so an agent can separate the two without opening a schema, though 'flags' remains slightly abstract.

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 second sentence names the alternative (kalshi_exchange_schedule) but only states what that sibling returns, not the condition under which this tool should be chosen over it. The routing is implied rather than explicit, so the agent must infer when status flags are the right call.

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