msf_session_destroy_all

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

The description explicitly says 'destroy', indicating a destructive action. However, no annotations are provided, so the description carries the full burden. It lacks details such as whether sessions are immediately terminated or if any confirmation is required. Adequate but minimal.

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?

One sentence, zero waste. Directly communicates the action. Concise without being incomplete.

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 simple action (destroy all sessions), the description is complete enough. Context indicates an output schema exists, so return values need not be detailed. However, for a destructive operation, a note on typical behavior (e.g., no undo) would improve completeness.

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?

Input schema has no parameters, so description adds no parameter information, which is appropriate. Schema coverage is 100%, and baseline is 3; description provides no extra meaning but is not lacking. It correctly implies no input is needed.

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 the verb 'destroy' and the resource 'all active Metasploit sessions', distinguishing it from sibling tool 'msf_session_destroy' which targets a single session. This provides specific purpose and differentiation.

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 (e.g., msf_session_destroy for individual sessions). No warning about destructive nature or prerequisites. The description only states the action without context.

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