snapshot_inram

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

With no annotations, the description carries the full burden. It discloses that the snapshots are an automatic ring buffer, supported actions, and that save/list/delete are not supported. It does not explicitly mention side effects (e.g., loading changes emulator state), but the term 'Time Machine' implies state restoration. This is still reasonably transparent.

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 two sentences, no redundancy, and front-loads the core purpose. Every word earns its place.

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's simplicity (2 parameters, no output schema), the description covers the essentials: purpose, supported actions, and limitations. It could mention the effect of 'load' on emulator state, but overall it is sufficient for an agent to use the tool correctly.

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%, so the schema already documents both parameters. The description adds minimal extra meaning by repeating the action mapping and index description, but does not significantly enhance understanding beyond the schema.

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 the tool accesses ZEsarUX in-RAM snapshots (an automatic ring buffer) and specifies the two supported actions: 'load' and 'get_index'. It distinguishes itself from sibling tools like load_snapshot and save_snapshot by noting that saving/listing/deleting are not supported.

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 explicitly lists supported actions and states that saving/listing/deleting are not supported over ZRCP, guiding the agent to use alternative tools (e.g., load_snapshot) for those operations. It also clarifies that position 0 is the oldest.

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