demote

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

Given the absence of annotations, the description takes on the burden of disclosing consequences by explaining that archived memories are 'only retrieved on demand via recall — not automatically injected.' This is meaningful behavioral context beyond the action itself, though it stops short of discussing reversibility or side effects.

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: action, consequence, and usage suggestion. No fluff; every word earns its place.

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 tool with one simple parameter and no output schema, the description covers the purpose, behavior, and when to apply it, fully addressing the likely questions an agent would have.

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 schema already describes the single 'id' parameter as 'Memory ID to demote' (100% coverage). The tool description does not add parameter-specific details, only context about the overall operation, so the baseline of 3 applies.

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 phrase 'Demote a memory from core to archive tier' uses a specific verb+resource pair, clearly distinguishing it from sibling tools like promote. The additional sentence about archive retrieval semantics further disambiguates what demoting entails.

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?

It explicitly states 'Use for memories that no longer need to be in every session,' giving a clear when-to-use signal. However, it does not mention when not to use it or name alternative tools such as 'promote' or 'forget'.

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