read_memory

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

With no annotations, the description only covers read operation basics and return format. It omits behavioral traits such as nondestructive nature, permission requirements, or potential side effects, leaving room for ambiguity.

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 concise, front-loaded with purpose, and uses a clear list for memory types. Every sentence adds value without redundancy.

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?

Despite explaining return JSON, the description neglects critical connection parameters and usage guidance. Given 8 parameters and many sibling tools, the description is incomplete for an agent to reliably invoke the tool.

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?

Only 3 of 8 parameters (memory, offset, length) are described with meaning and defaults. The remaining 5 parameters (device, tool, etc.) are undocumented. Since schema coverage is 0%, the description fails to compensate for the missing parameter semantics.

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 'Read raw bytes from a target device memory area' and lists specific memory types (flash, eeprom, etc.), making the tool's purpose precise and distinguishable from siblings like write_memory or erase.

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 explains parameters and return format but does not explicitly state when to use this tool versus alternatives (e.g., read vs. verify_hex). Usage context is implied but not guided.

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