lc_preview_delete_ai_memory

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

The description states 'Preview deleting' implying a non-destructive operation, but it does not explicitly confirm that no actual deletion occurs. The phrase 'through the partial-merge hook' is vague and adds no clarity about side effects or return behavior.

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 12-word sentence, which is brief. However, it lacks structure and fails to provide essential details, trading completeness for brevity.

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 five parameters, no output schema, and a network of sibling preview tools, the description is far from complete. It does not explain what a preview entails, what the partial-merge hook means, or how to interpret results.

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?

With 0% schema description coverage, the description must explain parameters. It only mentions 'ai_memory entry' but does not describe oid, agent, memory_name, partition_key, or token_ttl_seconds, leaving their purpose undefined.

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 verb 'Preview deleting' clearly indicates the action, and 'one ai_memory entry' specifies the resource. However, it does not differentiate from sibling lc_preview_delete_ai_memory_record, which also involves deletion preview but for a different entity.

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 provides no guidance on when to use this tool compared to alternatives like the actual delete tool or other preview tools. There is no mention of context or prerequisites.

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