ensp_cleanup_idle_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. It implies sessions are destroyed (清理), but it does not disclose scope (all devices vs. one), whether sessions are disconnected or merely removed, permissions required, or reversibility of the operation.

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?

A single front-loaded sentence with no filler; the threshold condition is stated immediately. It is terse to the point of under-specification, but nothing is wasted.

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?

An output schema exists, so return values need not be explained. However, for an unannotated destructive session operation, the description omits scope, side effects, and relationship to sibling cleanup/close tools, leaving significant gaps.

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 0%, so the description must compensate. It does explain the parameter's role relationally — sessions idle longer than idle_seconds are cleaned up — which adds meaning beyond the bare name, but gives no unit confirmation, default (300), or accepted range.

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 states a specific verb+resource: cleaning up (清理) sessions that have been idle beyond a threshold. It is clearly distinguishable from ensp_close_all_sessions by the idle condition, though it never names or contrasts that sibling explicitly.

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 the many session-management siblings (ensp_list_sessions, ensp_close_all_sessions, ensp_disconnect_device). The idle-threshold phrasing implies its use case but provides no explicit when/when-not or alternatives.

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