pwndbg_dw

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

No annotations are provided, so the description bears full responsibility. It only describes a read operation (dump) but does not disclose behaviors like address validity, session requirements, or error handling. The link to documentation adds some context but is insufficient.

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 relatively short but includes redundant sections like 'Args:' that repeat the schema. The source file and category add little value for an AI agent. Could be more streamlined.

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 output schema exists, return values are covered. However, the description lacks sufficient context about the tool's role among many memory dump siblings. It mentions '2-byte words' but does not clarify endianness or alignment. The external link provides additional completeness but is not fully integrated.

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%, yet the description merely lists parameter names and defaults without adding semantic details. For example, 'address' lacks format specification (e.g., hex) and 'count' defaults to 32 but units are implied. This does little 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 verb 'Dump' and the resource 'N words (2-byte) at address', with a WinDbg-style qualifier. This effectively differentiates it from sibling dump commands like pwndbg_db (byte), pwndbg_dd (double words), etc.

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 fails to provide guidance on when to use this tool versus alternatives. With many sibling dump commands, explicit selection criteria are needed, but none are given.

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