pwndbg_nextcall

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

With no annotations, the description carries the full burden. It mentions the breakpoint action, optional regex filter, and timeout parameter, but does not describe behavior when no call is found (e.g., continues?) or whether it modifies session state permanently. Adequate but not exhaustive.

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 front-loaded with purpose and includes a parameter list, source, category, and URL. While slightly verbose, the first sentence efficiently states the core function. Could be trimmed by removing the URL or source line.

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 low schema coverage, no annotations, and three parameters, the description is fairly complete. It explains parameters and purpose. However, it omits error cases (e.g., timeout expiration) and assumes basic debugging knowledge. An output schema exists so return values need not be explained.

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%, but the description documents all three parameters with clear explanations: session_id as UUID, symbol_regex as optional target filter, and timeout with default. This adds meaning beyond the schema's titles.

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 states 'Break at the next call instruction, optionally filtered by symbol regex,' providing a specific verb and resource. It distinguishes from sibling tools like pwndbg_next, pwndbg_nextjmp, and pwndbg_nextproginstr by targeting only call instructions.

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 breaking at call instructions but does not explicitly state when to use this tool over alternatives like pwndbg_next or pwndbg_nextsyscall. No exclusions or alternative tools are mentioned.

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