pwndbg_nextret

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

The description lacks behavioral details beyond breaking at returns. It doesn't disclose whether it sets a permanent breakpoint, modifies program state, or how execution continues. No annotations are provided, so the description carries full burden.

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 extremely concise, front-loading the primary purpose in one sentence, then efficiently listing source, category, and parameter details. No waste.

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 description provides essential purpose and parameter info, but lacks explanation of how the tool differs from pwndbg_stepret or any return value details. Given an output schema exists, some completeness is expected.

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 description explicitly explains both parameters: session_id as a UUID and timeout as seconds with default 30. Since schema coverage is 0%, this adds critical meaning beyond the 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 breaks at return-like instructions (ret, retf, iret, sysret), which is specific and distinguishes it from siblings like pwndbg_next (next instruction) or pwndbg_nextcall (next call).

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 vs. similar ones like pwndbg_stepret or pwndbg_next. The description does not provide context for selection.

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