达人效果汇总

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

注释已声明 readOnlyHint=true、idempotentHint=true、destructiveHint=false，描述本身未包含额外行为信息，但也没有矛盾。描述添加了具体计算字段的上下文，符合注释下应有水平。

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?

对于单参数工具且无输出 schema，描述提供了计算字段的清单，但未说明返回格式、聚合级别或数据范围。鉴于复杂度较低，描述基本可用但可补充更多细节。

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 在 schema 中仅有类型和长度约束，无描述。Schema 描述覆盖率为 0%，描述中未提及 report_id 的含义或格式，对单个参数缺乏任何语义补充，因此评分低。

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?

描述明确说明该工具计算达人视频数、花费、收入、订单、ROAS 和单均成本，动词'计算'搭配资源'达人效果'，清晰表达了核心功能。但未与兄弟工具（如 product_metrics_get、order_summary_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?

描述隐含了用于获取达人效果汇总数据的场景，但未明确说明何时使用此工具而非其他指标工具，如 product_metrics_get 或 order_summary_get。没有提供排除条件或替代工具指引。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.