compact_memory_delete

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

The description notes the destructive action ('삭제한다') and the required precondition, but does not elaborate on irreversibility, error states, or idempotency. Given no annotations, this is adequate but could be richer.

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?

Two sentences, no filler. The condition is front-loaded, and every sentence adds essential information. Extremely efficient.

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?

For a simple delete operation with one parameter and no output schema, the description covers the precondition, input constraints, and action. No gaps remain.

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 parameter 'ids' is described in the schema with snapshot reference. The tool description adds the crucial constraint 'only pass ids returned by compact_memory', which goes beyond the schema and clarifies proper usage.

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 ('삭제한다') and resource ('원본 log 기록'), and distinguishes its role as a cleanup step after compact_memory. No sibling tools are provided, but the purpose is unambiguous.

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?

Explicitly specifies the prerequisite condition ('compact_memory 후, principle 저장 성공 확인 후에만 호출') and the exact input constraint ('compact_memory가 반환한 id 목록만 전달하라'). This provides strong guidance on when and how to use the tool.

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