gdb_read_memory

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It fails to mention side effects (e.g., triggering hardware watchpoints or causing crashes on invalid addresses), required permissions, or whether the read is safe. The minimal description offers no behavioral context beyond the basic operation.

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 sentence, front-loaded with the key action. It is not verbose, but it is overly terse given the tool's complexity and the presence of three parameters. A slightly expanded description could improve clarity without sacrificing conciseness.

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 tool has an output schema, so return value details are not needed in the description. However, the description omits important context such as error conditions (e.g., invalid address behavior), the scope of memory (process vs. hardware), and any interaction with the debuggee state. This leaves the agent underinformed for safe and correct invocation.

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 coverage is 100%, so the schema already documents each parameter's purpose. The description adds no additional meaning beyond what the schema provides. It does not elaborate on constraints like address alignment or count limits, which would enhance parameter understanding.

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 action (read) and the resource (raw memory at an address). It is distinct from sibling tools like gdb_evaluate (expression evaluation) and gdb_raw_command (arbitrary commands). However, it lacks specificity about the memory context (e.g., debugged process memory), which slightly reduces clarity.

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 any conditions or limitations. For example, it does not explain when gdb_evaluate or gdb_raw_command might be more appropriate, or whether this tool is suitable for reading memory-mapped I/O or other special regions.

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