debug_read_memory

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

With no annotations provided, the description carries the full behavioral burden and it does convey the key trait: this is a non-mutating read operation. It also tells the caller the two possible return representations. It does not cover error behavior for unmapped or inaccessible addresses, but that is a secondary concern for a simple read primitive.

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?

One sentence contains the essential action, target, and return format with no redundant wording. It is front-loaded and immediately scannable.

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 rich schema covering address, count, format, and session ID, the description is adequate for invoking the tool correctly. Since there is no output schema, the description's mention of 'hex string' versus 'formatted hexdump' provides important return-shape 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?

All four parameters are already described in the schema, so schema description coverage is 100%. The description adds no parameter-specific detail beyond what the schema already provides, so the baseline score of 3 applies.

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 states a clear action ('Read memory'), specifies the target ('debugged process'), the location ('specific address'), and the output forms ('hex string or formatted hexdump'). The 'debugged process' scoping clearly separates it from static file reads like read_bytes.

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 establishes the intended context: live debugged process memory rather than static binary contents. It does not explicitly name alternatives or exclusion cases, but the process-scoped wording makes the correct use obvious among the many debug/read siblings.

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