mem_plugin

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

With no annotations provided, the description carries the full burden. It clearly states the tool is read-only and that VERDICT exposes no write primitive, and it lists refused behaviors (write plugins and output/dump flags). This is good transparency, though it could mention other behavioral aspects like error handling.

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 only two sentences, front-loaded with purpose and immediately followed by restrictions. Every word adds value, with no redundancy.

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 tool's complexity (3 params, no schema descriptions, has output schema), the description covers purpose, restrictions, and examples. It is fairly complete, though missing parameter format details are not critical due to the output schema.

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. It implies 'image' is the memory image and 'plugin' is a plugin name, and 'extra_args' can be used but without details. This adds some context but not enough to fully compensate for the missing schema descriptions.

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 runs a read-only volatility3 plugin by name to test a hypothesis. It distinguishes from sibling tools like mem_cmdline, which are specific plugins, making this a generic runner.

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 explicitly lists which plugins are appropriate (inspection plugins like pslist, netscan, malfind) and which are forbidden (write plugins like dumpfiles). It also states that output/dump flags are refused, providing clear guidance on when to use this tool vs alternatives.

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