sleep_replay

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

With no annotations, the description must disclose side effects. It implies mutation ('strengthen') but does not specify whether records are irreversibly modified, whether permissions are required, or what happens to existing data. It also fails to define 'surprising outcome records' or the format of the '历史成功率' summary.

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 concise sentence with no filler. It fronts the tool name and efficiently packs both actions into a compact structure.

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, output schema, or parameters, the description is the only source of information. It conveys the core function but omits critical context such as when to invoke it, how it integrates with sleep cycles, and what the output summary contains, which is insufficient given the large set of sibling tools.

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?

The tool has zero parameters, so no parameter explanation is needed. The baseline score of 4 applies, and the description does not attempt to describe nonexistent parameters.

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 identifies specific actions ('strengthen surprising outcome records' and 'consolidate each step's experience') with clear resources and an output ('历史成功率' summary). It partially distinguishes from siblings like 'sleep' and 'sleep_and_plan' by mentioning replay and consolidation, though it does not explicitly contrast them.

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 such as 'sleep' or 'sleep_and_plan'. The description only states what the tool does, leaving the agent to infer the appropriate invocation context.

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