cleanup_sessions

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

With no annotations, the description carries the full burden of behavioral disclosure. It signals destructiveness via 'complete reset of all data' but does not explain irreversibility, confirmation requirements, whether sessions are actively terminated, or what happens on failure. The schema later mentions confirm/dryRun, but the top-level description does not orient the agent to these safeguards.

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 short and avoids extraneous words, but 'Cleanup sessions:' merely restates the tool name. The phrase 'intelligent cleanup based on criteria' is a placeholder rather than a precise, front-loaded explanation, so the conciseness is achieved at the cost of substance.

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?

The definition is insufficiently complete for a destructive, mode-dependent tool. It does not explain return behavior, mode-specific guardrails such as confirm being required for 'all', or the consequences of a complete reset. The absence of an output schema and annotations makes this gap more significant.

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 description coverage is 100%, so the schema already documents all parameters, including the mode enum, force semantics, dryRun behavior, and confirm requirement for 'all' mode. The description adds only a high-level 'criteria vs reset' framing and no additional meaning beyond the schema.

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 identifies the action (cleanup) and the resource (sessions), and outlines two distinct modes: intelligent cleanup and complete reset. While 'intelligent cleanup based on criteria' is vague about what those criteria are, the tool is still distinguishable from the read-oriented sibling tools.

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?

There is no guidance on when to use this tool versus alternatives, nor any exclusions. The two modes are named but the conditions for choosing 'smart' versus 'all' are left entirely to the agent's interpretation, and no workflow context is provided.

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