Search ManaBuy products/games by keyword, product code, category, or hub URL name.
| Name | Required | Description | Default |
|---|---|---|---|
| pageNo | No | ||
| keyword | No | Search keyword, such as PUBG Mobile. | |
| category | No | Product category filter. | |
| pageSize | No | ||
| productCode | No | ManaBuy product code if known. | |
| gameHubUrlName | No | Game hub URL name if known. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only lists search criteria and does not state whether the operation is read-only, whether pagination is automatic, or what the return format is. The verb 'Search' implies read-only, but explicit disclosure is absent.
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 that front-loads the purpose and includes the key search dimensions. No wasted 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?
For a tool with 6 optional parameters and no output schema, the description is incomplete. It does not explain pagination behavior, result ordering, whether parameters are AND/OR combined, or what a response looks like. The tool may return a list of products, but this is not stated.
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 description lists the same search criteria that already have descriptions in the schema (keyword, category, productCode, gameHubUrlName), adding no new meaning. It fails to describe the pagination parameters (pageNo, pageSize) or how multiple filters interact. Schema coverage is 67%, which is moderate, so the description adds some value by summarizing but does not compensate for the missing parameter details.
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's function: 'Search ManaBuy products/games by keyword, product code, category, or hub URL name.' It specifies the resource (ManaBuy products/games) and the verb (Search), and lists the search criteria, which distinguishes it from sibling tools like get_product_detail that retrieve a specific product.
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 is provided on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or when to prefer search_products over siblings like get_order_detail or get_product_detail. The usage context is entirely implied.
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 or resource: auth (login/logout/status), product discovery (search/detail), ordering (quote/create/status/detail). There is no functional overlap that would cause an agent to select the wrong tool.
All tool names follow a consistent verb_noun pattern in snake_case, such as search_products, create_order, get_login_status. Even login_manabuy and logout_manabuy fit the pattern with the domain as the object.
With 9 tools, the server is well-scoped for the ManaBuy ordering domain. Each tool covers a necessary step in the workflow without redundancy or bloat.
The set covers product discovery, quoting, order creation, order status/detail tracking, and session management. A notable gap is the lack of a cancel order or list orders capability, but the core purchasing flow is complete.
