memory.reader_read

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

No annotations are present, and the description offers only 'Read integer values via BinaryReader,' which implies read-only behavior but does not disclose any side effects, required permissions, error conditions, or constraints. The agent cannot assess safety or potential impact.

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 a single sentence, which is concise, but it is under-specified and lacks key information. Brevity is not beneficial when essential context is missing, making this more underspecification than effective conciseness.

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?

Given the tool has 4 parameters with no schema descriptions, no output schema, and no annotations, the description is critically incomplete. It does not explain return values, error handling, prerequisites (e.g., an open session), or how to construct parameters, leaving the agent unable to use the tool reliably.

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 input schema has 0% documentation coverage across 4 parameters, and the description adds no explanation of what each parameter means (e.g., width as byte size, endian as byte order, address format, session_id purpose). The agent must guess parameter semantics, risking incorrect usage.

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 states 'Read integer values via BinaryReader,' which identifies the action (read) and resource (integer values via BinaryReader), but it does not clarify what BinaryReader is in this context or how it differs from sibling tools like memory.read. The purpose is vague and insufficient for selecting the correct tool.

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 is provided on when to use this tool versus alternatives such as memory.read or memory.writer_write. There are no conditions, prerequisites, or exclusions mentioned, leaving the agent with no criteria for appropriate invocation.

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