esil_get_memory

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

With no annotations, the description carries the transparency burden. It discloses the main side effect: creating a fresh session when session_id is absent. However, it does not mention session cleanup (e.g., esil_destroy), error behavior for invalid addresses/sessions, or the implications of leaving a fresh session active.

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 sentences with no filler. The core read action is front-loaded, and the session logic is stated compactly 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?

For a moderate-complexity tool with no output schema and no annotations, the description covers the primary action and session choice, but omits cleanup obligations, failure behavior, and return value specifics. It is adequate but not fully complete.

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 coverage is 100%, giving a baseline of 3. The description adds value by explaining the behavioral difference: using a persistent session versus creating a fresh one, which goes beyond the schema's note that binary_path is ignored when session_id is provided.

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 uses a specific verb and resource: 'Read memory contents from the ESIL emulated memory space at a given address.' It clearly distinguishes this from debug memory reads and RZIL variants by naming the ESIL emulated space, and it also communicates the session behavior.

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 provides clear conditional guidance: use a persistent session when session_id is supplied, and otherwise a fresh session is created. It does not explicitly name alternative tools or exclusions, but the session usage context is sufficiently clear.

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