pwndbg_strings

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

The description states it scans 'all readable memory pages' and 'extracts' strings, implying read-only access. However, it does not disclose performance implications (e.g., potential slowness on large memory), required permissions, or whether the process must be alive. With no annotations, the description carries full burden but lacks complete behavioral context.

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 concise (~80 words) and front-loaded with the core purpose. The inclusion of command source and category adds context but could be trimmed without losing essential information. Overall, it is well-structured and avoids fluff.

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 covers the core functionality and both parameters. Given the presence of an output schema (context signal), explicit mention of return values is unnecessary. However, it could be enhanced by noting that scanning all memory may be resource-intensive, but this is a minor gap.

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 provides brief descriptions for both parameters (session_id and n) and notes n's default value of 4, adding meaning beyond the schema's type and default. However, the descriptions are minimal and lack format or constraints (e.g., valid UUID format).

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 'Extract ASCII strings from readable memory pages' and explicitly compares to the Unix `strings` utility, making the tool's purpose unmistakable. It distinguishes itself from siblings like pwndbg_search (pattern search) and pwndbg_hexdump (hex view).

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 explains when to use the tool (to find ASCII strings in live process memory) and notes it is similar to the Unix `strings` command. However, it does not explicitly state when not to use it or mention alternatives like pwndbg_search for non-ASCII patterns, leaving some room for ambiguity.

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