websex_volatility

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

With no annotations, the description carries the full burden. It usefully discloses execution semantics: `vol` is invoked directly and shell parsing is never used, which tells the agent about argv handling and injection behavior. It omits permission requirements, side effects on the engagement namespace, and other behavioral traits, so it is adequate but incomplete.

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?

Three tight sentences with the core action front-loaded and no filler. Nothing is redundant, though it spends its limited space on execution mechanics rather than the parameter details that are missing elsewhere.

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?

An output schema exists, so return values need not be described. However, with zero schema coverage and no annotations, the description should compensate more for parameter meaning and behavioral context; it covers the execution model but leaves key gaps.

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% across 4 parameters, so the description must compensate and largely does not. It indirectly clarifies `arguments` (passed as raw argv tokens) and `working_directory` (use relative paths for engagement artifacts), but `stdin` and `engagement_id` are left entirely undocumented in both schema and description.

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?

States a specific verb and resource: run Volatility from the forensics toolkit. Volatility (memory forensics) is reasonably distinguishable from the other forensics siblings like binwalk, foremost, or scalpel. It never names those siblings, but the resource is specific enough that an agent can identify the tool's domain.

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?

No guidance on when to choose this tool over alternatives, and no prerequisites or exclusions. The only usage-flavored instruction is functional (run from the engagement namespace, use relative paths), not selective. An agent gets no help deciding when this applies versus the rest of the forensics family.

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