pwndbg_context

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 what sections are shown and mentions it's a read-only display command, but does not explicitly state no side effects, auth needs, or rate limits. The output schema exists but its details are not in the description.

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, starting with a one-liner purpose, then source/category, then details, and parameter list. Every sentence adds value; the length is justified by the need to describe a multi-section tool.

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 and the comprehensive description of purpose, sections, and parameters, the description is complete enough. It adequately covers what the tool does and how to use it, though usage comparisons could strengthen it.

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 fully compensates. It explains session_id as UUID and sections as space-separated list with example values like 'regs disasm stack backtrace', adding meaning beyond the schema's type definitions.

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 displays the pwndbg context — registers, disassembly, stack, backtrace, etc. It is specific about what it shows and distinguishes from sibling tools like pwndbg_stack or pwndbg_backtrace by positioning itself as the unified "signature command".

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 does not provide explicit guidance on when to use this tool versus alternatives. It mentions it's the signature command, but lacks when-not or comparison with other single-purpose context tools.

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