dump_module

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

No annotations are provided, so the description carries the full burden. It notes the action ('dump to disk') but does not disclose side effects such as whether it overwrites files, requires specific permissions, or alters the state of the debugger/IDA session. The minimal detail leaves significant behavioral ambiguity.

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 a single, front-loaded sentence that states the action and a key use case ('post-unpacking, etc.'). Every word earns its place; no redundancy or filler.

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?

For a simple two-parameter tool with a schema and output schema, the description is adequate but not rich. It lacks details on return values, error conditions, or overwrite behavior, and there are no annotations to compensate. The parenthetical gives a hint but not full 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?

Schema description coverage is 100%, with both 'module' and 'output' having descriptions and examples. The tool description adds no extra parameter meaning beyond the schema, so the baseline 3 is appropriate.

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 uses a specific verb and resource: 'Dump a loaded module to disk'. It clearly states the tool's function and the parenthetical 'post-unpacking, etc.' adds context. Among sibling tools, no other tool performs dumping, so it is well-distinguished.

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 phrase 'post-unpacking, etc.' implies a typical usage scenario but does not explicitly state when to use this tool over alternatives or provide exclusions. No alternative dump tools exist among siblings, so guidance is limited but not misleading.

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