pwndbg_heap

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

No annotations provided, so description carries full burden. It describes the behavior (walking heap, printing metadata) and defaults, but lacks details on output format, performance implications, required debug symbols, or that it only works with glibc heaps.

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 concise overall, with a clear first sentence and structured argument list. The technical source lines (pwndbg command, category) add noise for an AI agent but are not excessive.

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?

The description covers purpose and parameters adequately, but does not mention prerequisites (e.g., a running process or core dump) or the fact that it only works with glibc-based heaps. Given an output schema exists, missing output details are acceptable.

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%, but the description adds significant meaning: session_id is a UUID, addr is an optional arena or heap address, verbose shows extended chunk details. This goes beyond the raw schema types.

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 iteratively prints chunks on a heap, including metadata like size, flags, and pointers. It distinguishes itself from bin-specific tools (e.g., pwndbg_fastbins) but does not explicitly mention these siblings.

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 implies usage for inspecting heap chunks and defaults to current thread's active heap, but provides no explicit guidance on when to use this tool versus alternatives like pwndbg_bins, nor any conditions for not using it.

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