read_memory

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

With no annotations, the description carries the behavioral burden and does add useful context: accepted address forms and the output categories (hex, printable-ascii, unreadable ranges). However, it does not disclose length semantics, error behavior for invalid addresses, or whether a session_id is required, which limits 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?

Two sentences, action first, with concrete examples and no filler. The most important behavioral facts are front-loaded and every part of the text earns its place.

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?

Adequate for a small read tool: address forms and return categories are given. But without an output schema or annotations, the absence of length-unit and session_id behavior leaves material gaps for an agent deciding how to invoke it correctly.

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?

Address semantics are well explained beyond the schema, but schema description coverage is 0% and the description covers only one of three parameters. Length and session_id receive no explanation, so the agent still lacks crucial meaning for the other parameters.

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?

States a clear action and resource: 'Read raw memory from the inferior.' This is specific enough to distinguish from most siblings like read_registers or disassemble, but it does not explicitly name or differentiate sibling tools, so it falls just short of a 5.

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 intended use is implied by the verb and resource—when raw memory bytes are needed—but there is no explicit guidance about when to prefer it over alternatives like get_memory_map or read_registers, nor conditions such as requiring a running/stopped inferior or a session.

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