list_sessions

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that only live/warm sessions are returned and that bound accounts are included, which is useful, but says nothing about ordering, result size, pagination, or auth/permission requirements for a listing tool with no output schema.

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 short sentence that front-loads the verb and scope with zero filler. Every word, including "live warm" and "bound accounts," carries meaning.

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?

With no input parameters this is a simple listing tool, and the description conveys what is listed and one attribute of each item. However, with no output schema in place, it does not describe the shape of the returned session records or their volume, leaving the agent to infer the response.

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 are no parameter semantics to document and the schema cannot be richer than it is. Baseline 4 applies; the description does not add anything to explain, but nothing is missing either.

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 gives a specific verb and resource ("List live warm sessions") and scopes it with two qualifiers that narrow the meaning: "live warm" and "their bound accounts." An agent can tell this is a read-only enumerator distinct from open_session/close_session/session_turn, though it never names those siblings to make the contrast explicit.

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 statement of when to call this versus open_session, session_turn, or close_session, nor any prerequisite or context. The word "live" implies a current-state query, but that is inferred, not stated.

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