pwndbg_elfsections

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

With no annotations provided, the description carries the full burden. It indicates the tool reads the binary header and prints data, implying a read-only operation, but it does not explicitly state that it is non-destructive, whether permissions are needed, or any side effects. Important behavioral traits like idempotency or state changes are missing.

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 lead sentence, followed by command source, category, a short list of example sections, and parameter details. It is concise without unnecessary text, though the source and category lines could be considered extraneous metadata.

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 tool's simplicity and the presence of an output schema, the description covers the essential inputs and outputs adequately. It explains what the tool shows and what each parameter does. However, it lacks behavioral context and usage guidance, which slightly reduces completeness for an agent unfamiliar with pwndbg.

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 compensate. It explains `session_id` as the UUID of the session and `no_rebase` as showing file offsets instead of rebased addresses. This adds meaningful context beyond the schema's titles and types. However, it does not describe constraints or format expectations beyond what is implied.

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 'Print ELF section mappings from the binary header,' providing a specific verb and resource. It lists examples of sections and the information shown. However, it does not explicitly distinguish this tool from similar sibling tools like pwndbg_vmmap or pwndbg_got, which might also display address information.

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 lacks any guidance on when to use this tool versus alternatives. It does not mention prerequisites, suitable contexts, or situations where other tools would be preferred. The agent is left without context for decision-making.

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