cleanup_dead_sessions

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It clearly states that the operation kills sessions, defines the target as 'dead' sessions, and explains the optional age threshold and the immediate kill behavior when omitted. It does not discuss reversibility or side effects beyond killing dead sessions, but for this simple destructive cleanup tool, the core behavioral traits are adequately disclosed.

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 two sentences long and front-loaded with the primary action and condition. The parameter documentation is tight and directly explains both the optional flag and its default behavior. Every sentence earns its place with 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?

The tool is simple with one optional parameter and an output schema exists, so the description need not explain return values. It covers the action, target condition, and parameter semantics. However, it could slightly benefit from noting whether any sessions are affected if none are dead or if it ever touches active sessions, but the 'dead' condition implicitly covers this, making the description functionally complete.

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 only defines max_age_seconds as an optional integer/null with a default of null, providing no semantic meaning. The description adds full meaning: it specifies that the parameter filters sessions by how long they have been dead, and explicitly states the behavior when omitted ('all dead sessions are killed immediately'). This fully compensates for the 0% schema description coverage.

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 action ('Kill all sessions') and the specific condition ('where the SSH connection has closed'), making the scope explicit. It distinguishes itself from siblings like close_session (single session) and list_sessions (listing only) by targeting only dead sessions for bulk 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?

The usage context is implied by the description: run this when you want to clean up sessions whose SSH connections have closed. However, it does not explicitly mention alternatives or when not to use it, such as preferring close_session for individual active sessions, so guidance is only implied rather than explicit.

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