cigchat_shop_orders_get_info

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

With no annotations provided, the description carries the full burden. It adds the auth requirement ('Manage Team' scope) and the HTTP method (GET), which hints at read-only behavior. However, it does not disclose what data is returned, error handling, or potential side effects (even if none), leaving some behavioral ambiguity.

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, compact sentence that front-loads the purpose, includes the endpoint, and adds a critical auth requirement. Every word contributes meaning, with no redundancy or filler.

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 is simple (one parameter, no output schema), but the description still leaves gaps: it does not describe the return payload structure, possible error scenarios, or how this tool fits with order-related siblings like 'cigchat_list_orders' or 'cigchat_shop_orders_update'. Given the absence of an output schema, more detail on expected output would improve completeness.

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 already fully documents 'orderId' with a brief description ('Order Id'), and the endpoint path reinforces its role. The description adds no extra semantic value beyond confirming that orderId is the path parameter, so the baseline score of 3 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 uses a specific verb ('Get') and resource ('order info'), making the tool's purpose immediately clear. It also includes the exact endpoint path, which distinguishes it from sibling tools that fetch info for other entities (e.g., products, discount codes, locations).

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 required 'orderId' parameter implies this tool should be used when a specific order ID is known. However, the description does not explicitly state when to use this versus the sibling 'cigchat_list_orders' tool or any other alternatives, nor does it provide exclusions or context for selection.

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