product_metrics_getRetrieves SKU-level metrics including impressions, clicks, orders, units sold, revenue, CTR, conversion rate, and average order value from imported e-commerce reports.
按 SKU 汇总曝光、点击、订单、销量、收入、CTR、转化率和客单价。
| 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?
注释已声明readOnlyHint、idempotentHint和destructiveHint，描述未额外披露行为信息，但也没有矛盾。对于只读操作，描述没有增加实质性上下文，因此评分适中。
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?
单句描述，信息集中，没有冗余。简洁且直接列出了关键指标。
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?
只有一个参数，描述列出了汇总的指标，但没有说明返回格式或使用场景。对于简单工具，描述足够使用，但缺乏使用时机指导，完整性一般。
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?
描述未解释report_id的确切含义（是SKU还是报表ID），且schema描述覆盖率为0%，参数语义完全依赖描述，但描述未提供足够说明。
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?
描述明确说明按SKU汇总多个商品指标（曝光、点击、订单等），动词“汇总”和资源“商品指标”具体。但它没有明确与其他兄弟工具（如creator_performance_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?
没有说明何时使用此工具或何时不使用，也没有提及替代工具。尽管存在多个相关兄弟工具，描述未提供任何路由指导。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.