kde_session_list

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real scope information: only 'managed private' sessions are returned, and the private default is called out. It does not describe the result shape (how many sessions, how the default is signaled) or any empty-state behavior, so the added value is modest.

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 or repetition. It is perhaps overly terse - 'private default' is never defined, leaving the term to be inferred from context.

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 zero-parameter, non-destructive list operation the description covers the essentials, and annotations carry the safety profile. However, with no output schema, the description should say roughly what a result entry looks like and how the private default is marked; that gap leaves the agent guessing at the response shape.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. No parameter prose is needed and none is present.

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?

States a specific verb (list) and a specific resource (managed private KWin sessions), plus a secondary behavior (identify the private default). This distinguishes it from mutating siblings like kde_session_create, kde_session_stop and kde_session_use. It stops short of naming how it differs from kde_session_show, so it is clear but not fully differentiated.

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 explicit when-to-use statement or named alternative; the guidance is only implied by the verb 'list' and the 'managed private' scope. An agent can reasonably infer this is the discovery step before kde_session_use or kde_session_stop, but the description never says so.

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