pwndbg_stepsyscall

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

No annotations are provided, so the description carries full burden. It discloses single-stepping through instructions until a syscall is found and mentions branch-following. However, it does not detail potential side effects, stopping conditions (if no syscall occurs), or performance implications.

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 a clear header, one-line purpose, source/category info, a behavior explanation, and an Args section. It is concise and front-loaded, though the source and link could be deemed slightly extraneous.

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 presence of an output schema (context signal), the description does not need to explain return values. It covers purpose, differentiation from a sibling, basic parameters, and links to docs. It is adequate for the tool's complexity and sibling density.

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 schema has 0% description coverage, so the description must add meaning. It lists two parameters (session_id, timeout) and notes timeout's default value, but provides no additional semantics like format, validation, or purpose beyond the parameter names.

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 steps to the next syscall instruction and follows branches, using a specific verb and resource. It distinguishes from nextsyscall by noting the difference in branch handling.

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 explicitly compares with nextsyscall, explaining that this tool follows branches while the alternative does not. It implies usage for when branch tracking is needed but lacks explicit when-not-to-use guidance.

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