cleanup_expired

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

The description discloses the destructive action ('Delete all memories past their ttl') and the return behavior ('Returns count of deleted memories'). It also indicates intended frequency ('Call periodically'). No annotations are present, but the key behaviors are disclosed. It doesn't discuss irreversibility, but deletion semantics are implied.

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 three short sentences, each with a distinct purpose: action, return value, and usage recommendation. No wasted 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?

With no parameters and an output schema present, the description covers the core operation, return, and usage cadence. It's complete for a simple cleanup tool.

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 tool has zero parameters, so schema coverage is moot. Per the rubric, 0 params earns a baseline of 4.

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 uses a specific verb ('Delete'), identifies the resource ('memories'), and specifies the scope ('past their ttl'), clearly distinguishing this from sibling tools like 'forget' or 'list_memories'.

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 says 'Call periodically to keep memory clean,' providing a clear usage context. It doesn't mention alternatives or exclusions, but the periodic maintenance context is sufficient.

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