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

annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-call profile is clear. The description adds only that the payload concerns 'active and trading flags', which is modest extra context beyond the schema, and says nothing about freshness, caching, or failure behavior.

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 sentence fragment with no verb and no punctuation. It is short, but shortness here is under-specification rather than concision.

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?

An output schema exists, so return values need not be explained, and the tool has no inputs. What is missing is the operational verb and the reason an agent would call it versus kalshi_exchange_schedule, which leaves the tool's role only partially complete.

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 no parameters, so there are no parameter semantics for the description to explain; the baseline for zero parameters applies.

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 fragment 'Kalshi exchange active and trading flags' names the right subject and the resource (exchange flags), but never supplies a verb, so it is unclear whether the tool fetches, sets, or toggles these flags. Sibling tools such as kalshi_exchange_schedule are more explicit, so this one is under-differentiated.

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?

There is no when-to-use guidance and no mention of alternatives like kalshi_exchange_schedule. An agent has to guess why it would call this instead of the exchange schedule or a market status sibling.

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