pwndbg_nextjmp

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

No annotations exist; description states it continues to next jump but omits behavior on timeout or no jump found. Timeout param hints at some limitation but not enough 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?

Very concise: sentences explain action and use case, then lists args. Includes source and link. No wasted words.

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?

Covers purpose, params, and a link for details. Missing output format but output schema exists. Could mention prerequisites (session active) but overall adequate.

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?

With 0% schema description coverage, the description adds meaningful param info: session_id is UUID, timeout is max seconds (default 30). This compensates well.

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 breaks at the next jump instruction and specifies instruction types (jmp, je, jne, etc.) for tracing control flow. This distinguishes it from sibling like pwndbg_next or pwndbg_nextcall.

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?

It explains when to use it (tracing control flow decisions) but lacks explicit when-not-to-use or alternatives among similar step tools.

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