kalshi_get_trades

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, establishing the safe read-only behavior. The description adds useful context that the trades are 'public' and 'recent,' but it does not describe return format, pagination, rate limits, or any other operational behavior beyond what the annotations already cover.

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 concise sentence with no wasted words, with the core resource front-loaded. It is appropriately short for a simple tool, though it omits enough detail that the structure alone does not carry the full explanatory burden.

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?

This is a simple two-parameter read-only tool with rich annotations, and the description states the essential entity being fetched. However, with no output schema and no parameter-level guidance, the description leaves reasonable gaps around return values and limit semantics that an agent would need for precise 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?

Schema description coverage is 0%, so the description must compensate, but it only adds meaning for the ticker parameter: it identifies trades 'for a Kalshi ticker.' The limit parameter is not explained at all, leaving its semantics and default behavior undocumented outside the schema's default value.

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 description clearly identifies the resource ('recent public trades for a Kalshi ticker') and specifies the action of retrieving them. It is clear enough to distinguish from most siblings like kalshi_balance or kalshi_positions, but it does not explicitly name or differentiate against similar data-access tools such as my_fills or price_history.

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 guidance about when to use this tool versus alternatives such as my_fills, price_history, or kalshi_get_orderbook. The intended use case is vaguely implied by the name, but the description does not state exclusions, prerequisites, or context for choosing this tool over its siblings.

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