memory_hunt_process_anomalies

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions the use of Rust pslist+psscan and a Python analyzer, but it does not disclose whether the operation is read-only, what side effects may occur, what permissions are required, or what the output contains. This is insufficient for a tool that analyzes potentially sensitive memory dumps.

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 concise, consisting of two sentences. The first sentence states the purpose, while the second adds implementation detail. Both sentences are relevant, though the second is somewhat optional. It is appropriately sized without unnecessary fluff.

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?

For a tool with no output schema, the description gives a clear high-level functionality, but it lacks details about the return format, how anomalies are presented, or any caveats about memory dump compatibility. Given the complexity of memory analysis and the large sibling set, more context on expected outputs or limitations would be helpful.

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 provides 100% coverage for both parameters, so the baseline is 3. The description adds no additional parameter-specific meaning beyond what the schema already states; it does not explain how 'include_normal' affects results or how the image_path should be formatted.

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's purpose: detecting hidden processes, unusual parent-child relationships, and suspicious process attributes. It uses a specific verb ('Detect') and identifies the resource ('process anomalies'). However, it does not explicitly distinguish itself from sibling tools like memory_get_process_tree or memory_find_injected_code, though the focus on 'hidden processes' and 'suspicious attributes' differentiates it to some extent.

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 implies usage for process anomaly detection, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or scenarios where other tools would be more appropriate. No guidance on prerequisites (e.g., memory dump format) is provided.

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