sessions_list

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 behavioral disclosure. It states that the tool lists active sessions for the account, but it does not mention whether this is a read-only operation, what 'active' means, whether results can be paginated or filtered, or how this relates to session lifecycle or destruction.

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 focused sentence with no filler. It front-loads the action and resource immediately, and every word earns its place for a zero-parameter tool.

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 list tool with an output schema, the description is minimally sufficient: the agent knows what will happen, needs no arguments, and can rely on the output schema for return values. However, with no annotations and no mention of usage boundaries or behavioral details, the description is not fully complete for an unfamiliar agent navigating many session-related siblings.

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 accepts zero parameters and the input schema is fully documented, so there is no missing parameter meaning for the description to compensate for. The baseline for zero-parameter tools is 4, and nothing here lowers it.

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 a specific action ('List') and resource ('active sessions') with an account scope, so the agent knows what the tool does. It doesn't explicitly contrast itself with siblings like session_get, sessions_destroy, or login_history, but the wording is specific enough to avoid major ambiguity.

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 choose this tool over session_get, sessions_destroy, login_history, or session_state. The description only names the operation and provides no exclusions, alternatives, or context indicating the intended use case.

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