msf_session_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 disclosing behavioral traits. It only says 'List MSF sessions' and provides no information about whether this is read-only, what format the results take, or if it requires any existing state. This is a significant lack of transparency for a tool with no structured metadata.

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 one short sentence with no filler words. It is front-loaded with the action and target, making it efficiently structured for a tool with no parameters.

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?

Given the simplicity of the tool (no parameters, no output schema, no annotations), the description is minimally adequate. However, it lacks any context about what a 'session' entails, how results are returned, or when to use this over other tools. It is a bare minimum viable description.

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 has zero parameters, so the description does not need to explain parameter meaning. The baseline for a no-parameter tool is 4, and the description does not mislead or omit anything regarding inputs.

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 'List MSF sessions' uses a specific verb (List) and a clear resource (MSF sessions), distinguishing it from sibling tools like msf_session_create and msf_session_destroy. However, it does not specify the scope of listing (e.g., all sessions, active sessions), leaving a small gap in clarity.

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 alternatives. The description does not mention prerequisites, such as an active MSF connection, nor does it contrast with related tools like msf_session_execute or msf_session_destroy. The intended context is only implied by the tool's function.

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