pwndbg_hexdump

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

No annotations exist, so the description must fully convey behavioral traits. It states the tool shows memory in hex+ASCII format and lists output format options. However, it does not explicitly confirm the operation is read-only, nor does it mention any side effects, permissions, or limitations. The behavioral transparency is adequate but not comprehensive.

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 moderately concise, with a clear opening line, structured metadata (source, category), and an Args section. The inclusion of a link to external documentation adds value but could be trimmed. Overall, it earns its length without being verbose.

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 has 4 parameters, no annotations, and an output schema (not shown), the description covers the main functionality, parameter semantics, and output format. It lacks some behavioral details (e.g., whether the output is a string or structured), but the presence of an output schema reduces the need to describe return values. The link to documentation supplements completeness.

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?

With schema coverage at 0%, the description provides meaningful parameter descriptions beyond the schema. It explains session_id, address (with default $sp), count, and code (with format options 'py' and 'c'). This adds significant clarity, though details like the exact syntax for address (register names, expressions) are omitted.

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 performs a hex dump of memory at a specified address, resembling utilities like xxd/hexdump. It is specific about the verb 'dump' and resource 'memory at address', but does not explicitly distinguish from sibling tools like pwndbg_examine or pwndbg_search, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios, or exclusions. The parameter defaults (e.g., address defaulting to $sp) imply typical use, but the agent receives no explicit when-to-use or when-not-to-use context.

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