pwndbg_leakfind

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

No annotations are provided, so the description must disclose behavioral traits. It explains that the tool walks pointer chains and returns paths to interesting targets, but it does not mention side effects (e.g., memory reads), error conditions (e.g., no chain found), or prerequisites (e.g., debuggee running). The description lacks full behavioral detail.

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 structured with a summary line, metadata (command, source, category), a paragraph, an Args list, and a link. While mostly concise, the metadata lines may be unnecessary for an AI agent, and the link is a nice addition. Overall, it is well-organized without wasted sentences.

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 complexity and the presence of an output schema (though not visible here), the description covers the key aspects: purpose, parameters, and use case. It lacks details on return format or error handling, but the output schema likely fills that gap. The description is reasonably complete for an exploit development tool.

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?

Despite 0% schema description coverage, the description includes an Args section that explains each parameter: session_id, address (with default $sp), page_name, and max_depth (with default 4). This adds meaning beyond the bare schema, though it could clarify formats (e.g., address as hex string).

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 tool's purpose: 'Attempt to find a pointer leak chain from a starting address' and 'Walks pointer chains to find paths from a controlled region to interesting targets'. It uses specific verbs ('find', 'walks') and a specific resource ('pointer leak chain'), making it distinct from sibling tools like pwndbg_search or pwndbg_telescope.

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 mentions 'Extremely useful for exploit development', providing context on when to use it, but does not explicitly state when not to use it or list alternatives. No comparison to sibling tools is given, leaving the agent to infer usage boundaries.

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