connect_metasploit

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It only says 'Connect' without explaining what happens upon success or failure, whether a persistent session is established, or authentication details. This is insufficient for an agent to understand side effects or required state.

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 sentence, which is efficient but at the cost of necessary details. It is not overly long, but it sacrifices completeness for brevity. A balanced description would be longer but still concise.

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 there is no output schema, minimal parameters, and no annotations, the description should provide more context about the tool's purpose within the workflow, return values, or error conditions. It fails to do so, leaving the agent without enough information to determine if the tool is appropriate or correctly invoked.

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 add meaning beyond parameter names and defaults. It does not explain what host, port, or password represent, their expected formats, or how they influence the connection. The description adds zero value over the raw schema.

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 'Connect' and the resource 'Metasploit RPC server'. This is distinct from sibling tools, which focus on scanning, exploitation, and reporting, so the agent can immediately recognize this as a prerequisite connection tool.

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. No mention that it should be called before other Metasploit tools, no prerequisites, and no scenarios where it should not be used (e.g., if already connected).

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