metasploit_manage

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

There are no annotations to fall back on, so the description carries the full burden. It mentions 'Constraints' but only about parameter requirements, not about side effects (e.g., closing a session terminates the connection, stopping a job kills the process). No safety info is disclosed for destructive actions like close_session or stop_job.

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 concise and well-structured with 'Purpose', 'Constraints', and an 'Example'. It front-loads the main purpose and uses a compact enum-like list. Minor deduction for the trailing ellipsis which suggests possible truncation, but overall it is efficient.

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?

Even though an output schema exists (so return values are covered), the description lacks critical behavioral context for a management tool with destructive actions. It does not mention error handling, prerequisites (e.g., existing sessions), or confirmations. More detail on side effects and prerequisites is needed for safe usage.

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?

Schema description coverage is 0%, so the description must compensate. It does clarify conditional parameter requirements (session_id/command for interact_session, job_id for stop_job), giving meaning beyond the raw schema. However, it does not explain the purpose of timeout or the default behavior of job_id/session_id when 0.

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 tool 'Manage Metasploit sessions and jobs' and enumerates the specific actions via the action parameter. This distinguishes it from sibling tools like metasploit_search and metasploit_run_module by focusing on session/job lifecycle management.

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?

The description provides per-action parameter constraints (e.g., 'interact_session requires session_id and command'), which implicitly tells the agent which action to use based on available parameters. However, it does not explicitly state when to prefer this tool over alternatives or mention scenarios where it should not be used.

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