ReadMemory

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds some context about output format ('RE-friendly format') and that max_chars applies to text views, but does not disclose behavior for invalid/unmapped addresses or error conditions, so it adds modest value beyond the annotations.

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-line purpose statement up front, followed by a compact Args block. Every line adds information; nothing is redundant or padded.

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 read tool with no output schema, the description should clarify what 'RE-friendly format' actually returns (hex string, byte array, etc.) and how failures on unmapped memory are surfaced. It covers inputs well but leaves the output and error picture undefined, which is a noticeable gap given there is no output schema to compensate.

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 0%, so the description carries the full burden and does so well: it documents all four parameters, gives concrete address-format examples (`0x401000`, `module!func+0x10`, `[rbp+0x20]`), enumerates every valid value for ty, and clarifies that max_chars only affects ascii/utf8/utf16 decoding.

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 specific verb and resource: 'Read a memory range in a RE-friendly format.' An agent can immediately tell this reads memory (distinct from the MemoryWrite sibling). However, it does not differentiate itself from other read-oriented siblings like DumpPeFromMemory or DisasmRange, so it falls 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?

No when-to-use, when-not-to-use, or alternative guidance is provided. The agent must infer from the name alone that this is the generic memory-read tool versus DumpModule/DumpPeFromMemory/DisasmRange for specialized reads. No prerequisites or context are given.

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