kalshi_get_order_queue_position

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

Annotations already declare this as a safe read operation. The description adds behavioral context by explaining that queue position is determined by price-time priority and represents the amount of orders ahead in the match queue. It also specifies the HTTP method, reinforcing the read-only nature. No mention of error handling or rate limits, but the added context suffices.

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 two sentences plus the endpoint, with no redundancy. It front-loads the purpose, then explains the concept, and ends with the API call. Every sentence contributes value.

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?

For a simple single-parameter read-only tool with no output schema, the description explains what the tool returns (queue position as a count of orders to be matched). It omits details like error responses or exact return type, but for this complexity level, it is adequate. The read-only annotation and clear endpoint make it self-sufficient.

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 schema fully describes the sole parameter (order_id as a string with description 'Order ID'), giving 100% coverage. The description does not add further detail about the parameter's format or constraints beyond referencing it in the endpoint path. Baseline 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 description clearly identifies the tool as retrieving an order's queue position using a specific verb ('Get') and resource ('order queue position'). It explains the meaning of queue position, distinguishing it from the sibling tool 'kalshi_get_order_queue_positions' by focusing on a single order via order_id. The inclusion of the HTTP endpoint further clarifies the purpose.

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 provides context on when this tool is relevant: when checking how many orders need to match before a specific order is filled. It does not explicitly name alternatives or state when not to use it, but the singular 'order' and order_id parameter imply single-order queries, contrasting with the plural sibling. This is clear context without exclusions.

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