msf_session_create

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

With no annotations provided, the description carries full responsibility for disclosing side effects. 'Create' implies a state change, but there is no information about what happens when a session is created, whether resources are allocated, if it blocks, or if it starts background processes. No cleanup or lifecycle details are given.

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, short, front-loaded sentence with no filler. It communicates the core action immediately and uses zero unnecessary words, making it highly concise and well-structured.

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 tool with no parameters and no output schema, the description is insufficient to understand how to use the created session. It does not explain what a 'session' is, how to reference it later (e.g., via an ID), or whether it returns anything. The presence of sibling tools like msf_session_execute and msf_session_destroy creates expectations that are not addressed.

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 schema has zero parameters, so the description cannot add meaning to individual parameters. The baseline for zero-parameter tools is 4, and the description does not contradict or confuse this. However, it also does not clarify what 'msfconsole session' means, but that is not a parameter semantics issue.

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 clear action ('Create') and resource ('msfconsole session'), but the term 'session' is ambiguous without context—it could mean launching a console, establishing a Meterpreter session, or creating a session handle. It distinguishes from siblings (execute/list/destroy) but not enough to know exactly what is created.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing an active listener or a successfully exploited target, nor any indication that it should be used before msf_session_execute. The description only implies the action itself.

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