memory_dump_vad

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely says 'Examine' without stating whether it is read-only, what the return format is, potential side effects, or prerequisites. This is insufficient for a forensics tool.

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 is front-loaded with the core action, and every word earns its place. It is concise without being overly sparse, though it could be expanded with behavioral details without harming clarity.

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 3-parameter tool with no output schema and no annotations, this description is too minimal. It lacks details on output, workflow context, and how it differs from sibling memory-analysis tools. The 'useful for injected code regions' hint is not enough to guide an agent effectively.

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 descriptions cover 100% of parameters, so the baseline is 3. The description adds contextual meaning by interpreting VAD as 'memory region' and linking it to injected code, but it does not clarify parameter formatting or relationships beyond what the schema already provides.

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 uses a specific verb 'Examine' with a clear resource 'specific VAD (memory region)', which distinguishes it from sibling tools like memory_dump_process and memory_find_injected_code. However, 'examine' could imply a broader set of actions than just reading memory, leaving some ambiguity about the exact operation.

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 phrase 'Useful for injected code regions' implies a use case but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternative tools like memory_find_injected_code or memory_dump_process, so the agent must infer tool selection from minimal context.

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