edb_dump_memory_to_file

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

Description adds behavioral context beyond annotations: it writes to disk, specifies max size (1MB), and clarifies it's a file output operation. Annotations indicate non-read-only and non-destructive, which aligns. However, it does not mention overwrite behavior, permissions needed, or effects on the target process, which would improve transparency.

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 very concise: a single sentence for purpose, a line about use case, then a clean list of parameters. No unnecessary words. Structure follows a natural order: action, context, details.

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 simple interface (one parameter object, three fields), the description covers the core action but omits nuances like handling of invalid addresses, file existence, or process state requirements. The output schema exists (confirmation string) but is not detailed. More completeness would include error conditions and prerequisites.

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 input schema already provides clear descriptions for address, size, and file_path, including constraints like max 1MB. The description essentially repeats this information without adding new semantics. With high schema coverage, this is adequate but not enhanced.

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's action: 'Dump a memory region to a binary file on disk.' It distinguishes from siblings like edb_read_memory (which does not write to disk) by emphasizing the file output. The phrase 'Equivalent to EDB's memory dump feature' provides context and differentiates from other memory-related 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 mentions usefulness 'for extracting code regions, data sections, or heap contents for offline analysis,' which gives context but does not explicitly state when not to use it or compare with alternatives. It lacks guidance on prerequisites (e.g., process must be paused) or conditions that would make other tools more appropriate.

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