Retrieves a paginated list of the authenticated user's eSIM orders and history. Requires a valid session token.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Optional page number (defaults to 1). | |
| limit | No | Optional number of orders per page (defaults to 20). | |
| token | No | The secure session token returned by verify_agent_otp. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It only indicates a read operation and token requirement. It does not disclose any additional behavioral traits such as pagination behavior, data freshness, or error scenarios beyond what the schema already implies.
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 concise sentence with no superfluous words. It effectively communicates the core action. However, it could benefit from a brief note on response format.
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 no output schema, so the description should at least hint at the return structure (e.g., array of order objects). It does not. Given the lack of annotations and simple parameter set, the description is incomplete for an agent to fully understand the tool's output.
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 description coverage is 100%, so the baseline is 3. The description adds 'paginated' but this is already implied by the page/limit parameters. No additional semantic meaning is provided beyond the schema.
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 paginated list of the authenticated user's eSIM orders and history, which is a specific verb and resource. It distinguishes from sibling tools like cancel_order and purchase_esim_with_wallet that have different purposes.
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?
It mentions requiring a valid session token, which is a prerequisite. However, it does not provide guidance on when to use this tool versus alternatives like get_wallet_transactions or cancel_order, nor does it specify when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: order management, catalog browsing, wallet operations, authentication, and support. No two tools have overlapping purposes, making selection unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_esim_catalog, purchase_esim_with_wallet, verify_agent_otp). There is no mixing of conventions.
With 14 tools, the surface is well-scoped for an eSIM service: catalog browsing, purchasing, wallet management, authentication, order history, and support. No tool feels redundant or missing.
The set covers the core eSIM lifecycle (browse, buy, cancel, top-up, monitor usage, wallet, auth, support). A minor gap is the lack of a dedicated tool to retrieve a single order detail beyond the paginated list, but agents can work around.
