mem_vol2

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

No annotations exist, so description carries full burden. Discloses return format ('structured rows with PIDs, addresses, etc.'), behavior ('profile auto-detected and cached'), and constraints ('dump/output plugins and flags are refused'). This is good transparency, though minor details like error handling or performance are missing.

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 dense paragraph that avoids fluff. Each sentence adds value: lists plugins, explains auto-detection, return format, and constraints. However, it could benefit from minor restructuring (e.g., bullet points) for easier parsing by an agent.

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?

With 4 parameters, no annotations, and an output schema existing, the description covers return format and constraints adequately. It explains the auto-detection and caching behavior. It does not mention permissions or error handling, which would be helpful but not critical given the output schema provides return structure.

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 description must add meaning. It clarifies each parameter: 'image' is the memory image, 'plugin' is a Vol2 plugin, 'profile' can be empty for auto-detection, and 'extra_args' can be used but warns against dump/output flags. This provides essential semantics beyond 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 it runs Volatility 2 plugins for memory forensics on images Vol 3 cannot load, listing common plugins. It distinguishes from Vol 3, but does not explicitly differentiate from sibling tools like mem_processes or mem_plugin, which may have overlapping functionality.

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?

Explicitly states when to use: 'on images Volatility 3 cannot load'. Provides exclusions: 'Dump/output plugins and flags are refused' and recommends 'use read-only plugins'. Also explains profile auto-detection, guiding the agent on parameter handling.

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