volatility_linux

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: it specifies the tool is 'Read-only analysis' (indicating non-destructive operation), lists what it returns ('Returns plugin, profile, success, output, and errors'), and states a system requirement ('Requires volatility2 (vol.py) on PATH'). This covers safety, output format, and prerequisites well, though it lacks details on error handling or performance limits.

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 front-loaded with the core purpose in the first sentence, followed by return details and prerequisites. Each sentence adds essential information without redundancy, making it efficient and well-structured for quick understanding.

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 (memory analysis with external dependencies), no annotations, and no output schema, the description does a good job of covering purpose, behavior, and prerequisites. However, it could be more complete by detailing error scenarios or output structure, as the return values are listed but not explained in depth.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description does not add any additional meaning or context beyond what the schema provides for the parameters (dump_path, profile, plugin). It mentions the plugin in a general sense but does not elaborate on parameter usage or constraints beyond the 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 specific action ('Run a Volatility 2 Linux plugin against a memory dump') and resource ('memory dump'), distinguishing it from sibling tools like 'volatility_windows' by specifying the Linux focus. It provides a complete picture of what the tool does.

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 states when to use this tool ('Run a Volatility 2 Linux plugin against a memory dump') and mentions a prerequisite ('Requires volatility2 (vol.py) on PATH'). However, it does not provide guidance on when not to use it or name specific alternatives among siblings, such as 'volatility_windows' for Windows memory dumps.

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