pwndbg_dd

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

With no annotations, the description must disclose behavioral traits. It only describes the dump operation but does not state that it is read-only, what happens on invalid address, or any side effects. It fails to convey important behavioral context.

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 reasonably concise, front-loading the main purpose. It includes a source citation and link, which is extra but not excessive. The arg definitions are structured and clear.

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 simplicity and presence of an output schema, the description covers the basic functionality and parameters. However, it omits important context like error handling, read-only nature, and address formatting. Adequate but with 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 coverage is 0%, so the description must compensate. It explains session_id, address, and count with meaningful definitions, including the default for count. This adds value beyond the schema, though address format is not specified.

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 it dumps N dwords (4-byte) at an address in WinDbg style. This distinguishes it from sibling tools like pwndbg_dc, pwndbg_dw, pwndbg_dq, etc., which dump different sized units.

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 use this tool versus alternatives. It does not mention that other dump commands (db, dw, dq) exist or when to prefer dd, leaving the agent to infer based solely on the size.

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