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

注释已提供readOnlyHint=false、idempotentHint=true等，描述额外披露了会跑LLM并占用45秒状态锁、409处理方式、requestId幂等细节、note必填规则等，这些超越了注释。描述与注释一致，无矛盾。因为注释已覆盖基础信息，描述增加的是具体行为细节，故评4分。

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?

描述较长但组织清晰，分为【需要登录】【何时用】【组合链】【口径/坑】等部分，每句都有价值。虽然部分信息有重复（如note要求），但整体紧凑，没有冗余。评4分因为略显啰嗦但可接受。

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?

模式覆盖75%，但描述对每个参数都提供了额外语义：note必须写实际做了什么，outcome枚举三选一且缺note会被拒，actionId来源明确，requestId是幂等键且重试需原样重传。这些补充了模式未说明或说明不完整的内容，对调用至关重要。

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?

描述明确说明这是用于报告成长计划中某一步的真实结果，动词'报告'、资源'成长行动结果'，并指明前置是get_my_growth_plan中的步骤。与兄弟工具（如get_my_growth_plan）区分清楚，后者是获取计划，前者是回报结果。

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?

描述给出了明确的时机（真做掉之后）、组合链（get_my_growth_plan→取id→本工具→下一步），并明确提到'别并发'、'撞409别退避轮询'等排除条件，还指出了STARTED仅作为占位不应专门刷。提供了完整的使用语境和替代选择。

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