Clears merchant information from an order to reset or remove custom data.
Clear an Order's merchant information
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "ClearMerchantOrderInfoV3"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description only says 'clear', implying a destructive action, but provides no details on side effects, idempotency, permissions, or what 'merchant information' entails. No annotations exist to compensate.
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 extremely concise, but at the cost of missing critical information. It is front-loaded but not sufficiently informative for the tool's complexity.
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?
Given no annotations, no parameters, no output schema, and many siblings, the description is woefully incomplete. It does not explain what clearing means, the scope, or how the tool interacts with the order lifecycle.
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?
Input schema has zero parameters, but the description fails to explain how the order is identified or if there are implicit dependencies. This omission undermines usability.
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 the action (clear) and the resource (Order's merchant information), making the purpose clear. However, it does not differentiate from sibling tools like ClearMerchantOrderInfo or ClearMerchantOrderInfoListV3, lacking specificity.
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 on when to use this tool over alternatives, such as when to use V3 vs non-V3 or single vs list. Prerequisites or context for usage are absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.