openclaw_doctor_memory_dedupeDreamDiary

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

With no annotations provided, the description is the sole source of behavioral context. It states 'Mutates' but gives no details on side effects, permissions, reversibility, or idempotency. Important traits like potential impact on data or required authorization are absent.

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?

At two sentences and 13 words, the description is short, but it sacrifices informative content for brevity. It front-loads the purpose but omits crucial details about behavior and parameters, earning a middling score for under-specification rather than efficient conciseness.

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 the complexity of deduplication, no output schema, and no annotations, the description is insufficient. It fails to explain what happens after deduplication (e.g., no return value mentioned), error conditions, or how duplicates are identified. The agent lacks context to use the tool reliably.

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 input schema covers the sole defined parameter 'instance' with a clear description, achieving 100% coverage. However, the description does not mention this parameter or address the unusual 'additionalProperties: true' setting, which allows arbitrary extra parameters without explanation. The agent is left uncertain about what actual data inputs are needed for deduplication.

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 clearly states the verb 'deduplicate' and the resource 'dream diary entries'. While it distinguishes from sibling tools like 'openclaw_doctor_memory_dreamDiary' by the specific operation, it does not elaborate on what 'dream diary entries' are or provide boundaries, which is acceptable given the tool name provides context.

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?

The description offers no guidance on when to use this tool versus alternatives (e.g., backfill, repair, reset). It does not specify prerequisites, conditions, or exclusions, leaving the agent to infer context from the tool name alone.

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