pwndbg_nearpc

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

No annotations are provided, so the description carries the burden. It explains the enhanced disassembly behavior, inline annotations, and emulate option. However, it does not explicitly state that it is a read-only operation, which is implied but not confirmed.

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 well-structured with clear sections, including purpose, aliases, source, and parameter list. It is informative without being excessively long, though some details (e.g., category) may be less relevant.

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 tool is moderately complex with 4 parameters and an output schema. The description covers key features and parameters but misses explicit comparison to sibling disassembly tools and does not explain when to use the 'emulate' option. An external link is provided for further detail.

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 description coverage is 0%, so the description must add meaning. It explains the address default as $pc, lines as number of instructions, and emulate as predicting register values. session_id is only described as 'UUID of the session', which adds little beyond schema.

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 disassembles instructions near the PC with enhanced annotation, listing specific features like resolved symbols and register values. However, it does not explicitly differentiate from the sibling tool 'pwndbg_disassemble', which likely provides similar basic disassembly.

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?

No guidance on when to use this tool versus alternatives like pwndbg_disassemble. It describes default parameter values but lacks context on when the enhanced features are beneficial or necessary.

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