pwndbg_load_core

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

With no annotations, the description must disclose behavioral traits but only states the action. It omits side effects, prerequisites (e.g., executable matching core), or changes to debugger state, leaving significant gaps.

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 brief with a clear one-line purpose followed by a bulleted arg list. Every sentence adds value, and the purpose is front-loaded with no waste.

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 an output schema and is a load operation, the description covers basic usage but lacks context about prerequisites (e.g., core and executable compatibility) and post-load state. More detail would help, especially with no annotations.

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?

Despite 0% schema description coverage, the description adds meaningful param descriptions (e.g., 'The UUID of the session', 'Path to the executable that generated the core'), which compensate well. However, no format or constraint details are provided.

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 loads a core dump file for post-mortem analysis, using a specific verb and resource. The name and description distinguish it from siblings like pwndbg_attach or pwndbg_load, though it does not explicitly differentiate from pwndbg_load.

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, such as using pwndbg_attach for live processes or pwndbg_load for executables. It lacks any 'when not to use' or context for selection.

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