read_memory

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

No annotations are provided, so the description carries the full burden. It only states 'read' which implies a read-only, non-destructive operation, but does not disclose other behavioral traits like whether it requires the target to be halted or if it affects processor state. The description is minimal but non-contradictory.

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 extremely concise with three sentences: the purpose and two parameter explanations. Every sentence serves a clear purpose without any filler or redundancy. The key purpose is front-loaded.

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 having no annotations, the description covers parameters adequately and the required schema output exists (so return value explanation is not needed). However, it could mention prerequisites like needing an active connection, which would improve completeness. Overall adequate for a simple 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?

The schema description coverage is 0%, but the description fully compensates by explaining both parameters: address format ('hex 0x... or decimal') and word_size values ('8, 16, or 32'). This adds significant meaning beyond the bare schema definition, which lacks descriptions entirely.

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 starts with 'Read a single value from memory,' clearly stating the action (read), resource (memory), and scope (single value), which distinguishes it from sibling tools like read_memory_block that read multiple values.

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 does not provide explicit guidance on when to use this tool versus alternatives. While the name and description imply use for single addresses, no 'when-to-use' or 'when-not-to-use' context is given. Sibling differentiation is implicit through parameter descriptions.

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