pwndbg_expression

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether the operation is read-only, if it requires a running session, or what the side effects are. The minimal description fails to inform behavioral expectations beyond a basic read.

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 exceptionally concise: two sentences for the purpose and two lines for parameter documentation. It is front-loaded and structured, with no redundant words. However, its brevity comes at the cost of completeness.

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 many sibling tools (100+) and the need for context in a debugger, the description is incomplete. It does not explain prerequisites (e.g., active session), return value (though output schema exists), or differentiate from expression-related siblings. The tool's simplicity (two params) is not sufficient justification for this lack of context.

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 0% schema coverage, the description adds little value. It repeats parameter names and types already in the schema, only clarifying that session_id is a 'UUID' (marginally helpful) and expression is 'the expression to evaluate'. No format, language, or examples are given, so the semantic gain is minimal.

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 verb 'evaluate' and resource 'expression in the current frame (LLDB native)', making the purpose unambiguous. However, it does not differentiate from similar siblings like pwndbg_print or pwndbg_emulate, which could cause confusion in a large set of tools.

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, nor when not to use it. It merely describes the action without context, leaving the agent to infer usage from the name and siblings.

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