imgui_list_snapshots

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. As a list/read operations, it implies non-destructive behavior, but the description doesn't explicitly state whether this is a safe read-only operation or describe the exact return format. It does state what information is returned (names, frame numbers, widget counts), which adds some transparency, but doesn't disclose ordering, snapshot limit behavior, or interaction with load/save/delete siblings.

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 clear sentence with no filler. It efficiently states the purpose and the data content of the listing. This is appropriately concise.

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 zero-parameter list operation, the description adequately covers what the tool does and what it returns. No output schema exists, so the description noting it returns names, frame numbers, and widget counts helps offset the lack of output schema. The snapshot management family (list/load/save/delete) is clear from the name and sibling context.

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 tool has 0 parameters and 100% schema description coverage (coverage is vacuous with no params). Per the rubric, 0 params gives a baseline of 4. The description correctly indicates this is a no-input listing operation, requiring no parameter documentation.

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 ('List') plus a resource ('all saved snapshots') and specifies the data returned (names, frame numbers, widget counts). It clearly distinguishes from siblings like imgui_save_snapshot, imgui_load_snapshot, and imgui_delete_snapshot by making it a pure enumeration operation.

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 doesn't provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternatives. It's clear the tool is for enumeration ('List all saved snapshots'), and from context signals one can infer it complements the snapshot lifecycle tools, but there is no explicit exclusion guidance such as 'use before loading a snapshot' or distinction from other listing tools like imgui_list_scenes or imgui_list_fonts.

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