kalshi_get_order

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description does not contradict this. It adds the HTTP method and path (GET /portfolio/orders/{order_id}), which confirms the read-only nature but provides no details on return format, errors, or authentication. With annotations covering the safety profile, this is adequate but not rich.

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 brief (two sentences) and front-loaded with the purpose. It avoids unnecessary fluff, though 'Endpoint' is slightly redundant. Overall, it is efficient and easy to scan.

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 read-only getter with one parameter and no output schema. The description provides the endpoint and a basic purpose, but lacks any explanation of what the response contains or how it relates to other order endpoints. It is marginally adequate for the complexity level.

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 coverage is 100% with order_id described as 'Order ID'. The description only references the parameter in the endpoint path, adding no new meaning beyond the schema. Baseline score of 3 is appropriate because the schema fully documents the parameter.

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 the tool retrieves a single order, using 'Get' as the verb and specifying 'single order' to distinguish from list endpoints like kalshi_get_orders. The inclusion of the endpoint path reinforces the resource. Minor redundancy with 'Endpoint' but overall specific.

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?

No guidance on when to use this tool versus kalshi_get_orders or other related tools. The 'single order' wording implies the scope but does not explicitly state exclusions or alternatives, so the agent gets no directional support.

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