pwndbg_dds

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

No annotations provided; describes dumping and symbol resolution but does not disclose any behavioral traits like side effects, permissions, or state changes.

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?

Extremely concise: three sentences for core purpose, plus minor details (aliases, source, category, args). Front-loaded and no unnecessary content.

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?

Adequate for a simple two-parameter tool: explains purpose, usage context, and parameters. Lacks output schema description, but the stated behavior ('Shows pointer-sized values') gives sufficient expectation.

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?

Description includes parameter explanations for session_id ('UUID of the session') and addr ('Address to dump'), adding meaning beyond schema titles and types, compensating for 0% schema coverage.

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 'Dump pointers and resolve symbols at address (WinDbg-style)' and distinguishes from sibling tool pwndbg_telescope by noting the WinDbg format.

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?

Mentions similarity to telescope, implying when to use this tool (prefer WinDbg format), but lacks explicit when-not-to-use or alternatives beyond that.

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