supersede

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

Without annotations, the description discloses key behavioral effects: preserves history for audit and drops old memory's retrieval score. It also mentions un-superseding capability. Could be more detailed on error cases or side effects, but adequate.

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?

Three concise sentences, front-loaded with action, usage condition, and preference over alternative. No unnecessary words.

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 context of many sibling tools, the description provides enough context on when to use this over alternatives. Output schema exists (not shown) so return values are covered. Missing full parameter documentation, but overall sufficient for moderate complexity.

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?

Schema coverage is 0%, so description must compensate. It explains 'superseded_by' (pass None to un-supersede) but does not explain 'reason' parameter at all. 'memory_id' is inferred but not explicitly described.

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 tool's action: 'Mark a memory as superseded by a newer one.' It differentiates from sibling tools like 'forget' by explicitly preferring supersede for preserving history and retrieval score adjustment.

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 states when to use ('USE THIS WHEN: a fact has changed...') and when to prefer over alternatives ('PREFER THIS over forget'). Also provides guidance on un-superseding via 'superseded_by=None'.

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