batch_get_ordersFetch detailed information for multiple orders in one request. Provide the app package name and a list of order IDs (1-1000) to retrieve order details.
Get detailed information for multiple orders at once.
| Name | Required | Description | Default |
|---|---|---|---|
| order_ids | Yes | List of order IDs to retrieve (1-1000) | |
| package_name | Yes | App package name |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.4.0Does 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 only says 'detailed information' and 'at once,' and does not mention how missing or invalid order IDs are handled, whether results preserve input order, or any rate-limit or payload considerations.
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, tightly written sentence with no filler. The key qualifier 'multiple' is front-loaded and immediately signals the batch nature of the operation.
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 batch-get operation with a full input schema and an output schema, the description is minimally adequate. However, it leaves gaps around behavior for nonexistent order IDs, partial success semantics, and whether the response corresponds directly to the requested order list.
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 has 100% description coverage for both package_name and order_ids, including the 1-1000 limit. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 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 states a clear action and resource: getting detailed information for multiple orders at once. The word 'multiple' helps distinguish it from the sibling get_order tool, though it does not explicitly name that alternative.
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 phrase 'multiple orders at once' implies this tool is intended for batch retrieval rather than single-order lookup. However, it provides no explicit guidance on when to choose this over get_order or any related order tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.