get_order_detail

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Get details' which implies a read operation, but it does not mention any side effects, authentication requirements, error conditions, or rate limits. This is insufficient for a tool with no annotation fallback.

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 that is both concise and informative. It front-loads the purpose and immediately states the parameter requirement. No unnecessary words.

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?

The tool has 4 parameters with 1 required, moderate complexity. Without an output schema, the description could mention the return format or typical fields. However, the tool's purpose is simple and the description adequately covers the input constraints. It is minimally complete but could be enhanced.

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 input schema has 100% coverage with descriptions for all parameters. The description adds crucial semantics by clarifying that exactly one of orderId, clientOrderId, or algoClientOrderId is required, which is not captured in the schema required field (only instId is marked required). This is a valuable addition.

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 'Get details of a specific order' which is a specific verb+resource combination. It distinguishes from sibling tools like get_open_orders and get_order_history by focusing on a single order and mentioning required identifiers.

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 minimal usage guidance by stating that one of orderId, clientOrderId, or algoClientOrderId is required. However, it does not explicitly explain when to use this tool versus alternatives like get_open_orders or batch_orders, leaving the agent to infer from context.

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