vol_psscan

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal the scanning technique (pool scan) and its special capability to find hidden/terminated processes, which is useful. Yet it does not address potential side effects, permissions, or limitations, leaving notable transparency gaps.

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 that leads with the plugin name and immediately states the tool's purpose. Every word earns its place, making it highly concise and well-structured.

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, the description is insufficient for a complex Volatility operation. It lacks parameter explanations, prerequisites, usage alternatives, and any annotation support, making it inadequate for safe and correct invocation.

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?

The input schema has zero description coverage for 'source' and 'image_path', and the description does not mention either parameter. Neither the schema nor the description clarifies what 'source' means or how the two parameters relate, leaving the agent without needed guidance.

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 identifies the tool as running the Volatility 3 windows.psscan plugin and states its specific function: 'pool-scanned processes (finds hidden/terminated).' This distinguishes it from siblings like vol_pslist, which lists standard processes, by emphasizing its unique ability to discover hidden or terminated processes.

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 a clear context for when to use this tool: when seeking hidden or terminated processes. However, it does not explicitly mention alternatives or define when not to use it, so it lacks the explicit exclusions that would earn a 5.

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