order_summary_getRetrieve a comprehensive order summary including sales, revenue, refunds, average order value, and country distribution from imported JSON reports.
汇总订单、销量、收入、退款、客单价和国家分布。
| Name | Required | Description | Default |
|---|---|---|---|
| report_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the aggregation scope but does not disclose additional behavioral traits such as dependencies on imported reports, return format, or limitations beyond the metric list.
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 sentence that front-loads the verb '汇总' and quickly lists all covered metrics without filler. It is appropriately concise, though the brevity sacrifices parameter and usage detail.
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?
With one required parameter and no output schema, the description does not explain what report_id refers to or what the summary output looks like beyond the metric names. Annotations cover the read-only/idempotent nature but not invocation context, leaving the agent under-informed.
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 0% and the description never mentions report_id or explains how to obtain or format it. Because coverage is low, the description was expected to compensate with parameter guidance, but it provides none.
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, '汇总' (summarize), and clearly identifies the resource as order business metrics, enumerating orders, sales, revenue, refunds, average order value, and country distribution. It is unambiguous about the tool's purpose, though it does not explicitly differentiate it from sibling tools like report_list or product_metrics_get.
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; there are no exclusions, prerequisites, or references to sibling tools. The metric list implies it is for order-level summaries, but the agent must infer the appropriate selection context on its own.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.