cleanup_old_sessions

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

With no annotations, the description must disclose behavioral traits. It states 'Remove' (destructive) but does not mention irreversibility, scope (does it affect only sessions or related data?), permissions required, or side effects. The schema adds a default of 30 days, but the description itself lacks critical safety context.

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, concise sentence of six words: 'Remove sessions older than specified days.' It is front-loaded with the action and resource, with no filler or redundancy.

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 destructive cleanup tool with one parameter and no output schema, the description is too sparse. It does not explain what qualifies as 'older', whether the operation is permanent, or what happens to related contexts (e.g., session memory). This is a significant gap given the lack of annotations.

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 100% for the single 'days' parameter, which includes a description and default value. The tool description adds no extra meaning beyond what the schema provides, so it meets the baseline but does not enhance parameter understanding.

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 ('Remove') and resource ('sessions') with a clear condition ('older than specified days'). It is unambiguous and distinguishes itself from sibling tools like store_session_context or retrieve_session_context, which handle session creation/retrieval, not cleanup.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., whether this is for maintenance), nor any exclusions or alternative tool referrals. The description simply states what it does, leaving the agent to infer usage context.

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