pwndbg_dq

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

No annotations provided; description only states the action. Fails to disclose side effects, error handling (e.g., invalid address), or that it is a read-only operation.

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?

Reasonably concise with a clear one-sentence purpose. Includes source file and link, which add clutter but are not excessive. Front-loaded with the key action.

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?

Output schema exists, so return values are covered elsewhere. Description covers parameters adequately but misses expected output format (e.g., hex dump). Overall sufficient but not thorough.

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 0% so description must compensate. Provides minimal definitions: 'Address to dump' and 'Number of qwords (default: 8)'. Adds default and unit but lacks validation hints or format details.

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?

Clearly states the verb 'Dump' and resource 'N qwords (8-byte) at address'. Differentiates from siblings like pwndbg_dd, pwndbg_dw by specifying the unit (qwords) and WinDbg-style notation.

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?

Implies usage for dumping memory, but lacks explicit guidance on when to use vs. alternatives (e.g., other memory dump commands). No when-not-to-use or exclusion criteria.

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