memory_read

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

Description does not mention any side effects, error behavior for invalid addresses, or permissions required. With no annotations, the description fails to disclose these important behavioral traits.

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 concise sentences with no wasted words. Could be slightly improved by structuring use cases or examples, but remains efficient.

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 simple read operation with two parameters and an output schema. However, lacks behavior details for edge cases and does not differentiate from the pointer chain variant, leaving some gaps.

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?

Explicitly lists allowed type_name values, adding value beyond the schema. However, address_hex format (e.g., '0x' prefix) is not described, and schema coverage is 0%, so the description only partially compensates.

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?

Description clearly states 'Read a typed value at an absolute address' and lists valid type names. This is a specific verb+resource combination that distinguishes it from sibling tools like memory_write or memory_read_pointer_chain.

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 guidance on when to use this tool versus alternatives. Does not explain prerequisites (e.g., memory_attach required) or when not to use it.

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