remote_session_cleanup_idle

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

No annotations are provided, so the description carries the full burden. It states that sessions are closed but does not disclose that this is a destructive operation, potential side effects, or whether any confirmation is required. The term 'named sessions' is also ambiguous without further explanation.

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 that front-loads the action and condition. It contains no wasted words, though it is slightly too terse to fully convey behavioral nuance.

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 simple tool with one parameter, the description provides the core action and condition. However, it lacks warnings about the destructive nature of closing sessions and does not explain the behavior when no sessions are idle or when multiple sessions match. The presence of an output schema reduces the need to describe return values, but the description still leaves gaps in operational context.

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 description clarifies max_idle_seconds as the 'requested number of seconds', which maps directly to the parameter. However, it does not add detail about acceptable values, the default of 3600, or how the threshold is applied. With a single parameter and 0% schema description coverage, this is adequate but minimal.

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 ('Close') and the resource ('named sessions'), with a specific condition ('idle for at least the requested number of seconds'). This distinguishes it from siblings like remote_session_close and remote_session_close_all by adding the idle-time filter.

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 description implies usage when idle sessions need cleanup, but it does not explicitly mention alternatives or provide when-not-to-use guidance. Sibling tools like remote_session_close or remote_session_close_all are not referenced, so the agent must infer the appropriate context.

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