msfconsole

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 behavioral disclosure. It only gives the high-level purpose and a generic output note; it does not mention non-interactive execution via the command argument, resource file behavior, side effects, or the destructive potential of running exploit and post-exploitation modules.

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 front-loaded with the core purpose, followed by useful sibling disambiguation and an output summary. Minor redundancy exists in 'without the console' versus 'without opening console,' but every sentence earns its place.

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 powerful and potentially destructive tool, the description covers what the tool does, when to use it, and what output to expect, while the schema covers parameters. Missing context includes the non-interactive execution model and safety expectations, making it adequate but not comprehensive.

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 100%, so command, opts, and resource_file are already documented, including the override behavior. The description adds no parameter-level meaning beyond that, which is acceptable at the baseline.

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 specific verb and resource: 'primary interface for running exploit, auxiliary, post-exploitation, and payload modules.' It also explicitly distinguishes sibling tools by directing standalone payload generation to msfvenom and module search to msf_search, so an agent can tell them apart.

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 gives explicit usage context: 'Use to execute exploits, scan with auxiliary modules, or run post-exploitation tasks.' It names alternatives with their conditions, such as msfvenom for standalone payloads and msf_search for searching modules without opening the console.

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