kalshi_market

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns orderbook and trades but does not mention rate limits, authentication needs, read-only nature, or any side effects. The behavioral picture is incomplete for an agent to safely invoke this tool.

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 repeats the same sentence verbatim, wasting space. The example is useful but not enough to compensate for the redundancy. The description could be more streamlined.

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?

Given the absence of an output schema, the description should explain the structure of the returned data (e.g., orderbook levels, trade fields). It does not provide this information, leaving an agent uncertain about how to handle the output. The tool's complexity is moderate but the description is insufficient.

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?

All three parameters are described in the input schema (100% coverage). The description does not add significant new semantics beyond the schema, but the included example clarifies the expected format for the ticker parameter. The schema already provides adequate parameter definitions.

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 states it returns orderbook depth and recent trades for a specific Kalshi market ticker. It provides a concrete example URL. However, it does not explicitly differentiate from sibling tools like 'kalshi_probability' or 'orderbook', leaving ambiguity about when to use this tool over others.

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 description lacks any guidance on when to use this tool versus alternatives. No context is given about prerequisites, preferred use cases, or situations where this tool is not appropriate. The example helps with syntax but not decision-making.

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