pwndbg_plist

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the tool 'dumps' and 'displays' elements, but does not mention whether it modifies state, requires permissions, or has side effects. The description is insufficient given the lack of annotations.

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, with a short opening sentence, a bulleted list of parameters, and a link. It includes some extraneous metadata (source file, category) but remains focused. The structure is front-loaded and easy to parse.

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 and parameters are fully described, the description provides sufficient context for using the tool. It could mention error handling or behavior when the path is invalid, but overall it covers the essential functionality for a linked list dumper.

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?

The input schema has 0% description coverage, so the description must explain parameters. It provides meaningful descriptions for all four parameters: session_id, path, next_field, and count, adding context like 'UUID', 'Starting address', 'Name of the next pointer field', and 'Optional maximum number'. This fully compensates for the schema gap.

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 'Dump elements of a linked list structure' and describes walking a linked list starting at a path. This verb+resource pairing is specific and distinguishes it from sibling tools like pwndbg_telescope or pwndbg_hexdump.

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 explains the tool walks a linked list and accepts parameters for starting address, next field, and count. However, it does not specify when to use this tool over alternatives, nor does it provide exclusions or prerequisites. The context is clear but lacks explicit usage boundaries.

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