imgui_delete_snapshot

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

No annotations exist, so the description must carry the full behavioral burden. It doesn't state that this is a destructive, irreversible operation, what happens if the name is not found, or whether deletion affects any dependent state. This is a meaningful gap for a mutation tool.

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?

One clean, efficient sentence. No wasted words. The brevity is appropriate for a simple single-parameter operation, even if more behavioral detail would improve completeness.

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 destructive tool with zero annotations, no output schema, and no behavioral disclosure beyond 'delete,' the description is incomplete. It should at minimum address irreversibility and missing-name behavior. The single sentence is insufficient for a mutation operation.

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 single name parameter is fully documented in the schema (100% coverage: 'Name of the snapshot to delete'). The description adds no additional syntax, format, or constraint details, so baseline 3 applies.

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 a clear verb+resource pair ('Delete a saved snapshot by name'). It is unambiguous and correctly distinguishes from siblings like imgui_load_snapshot, imgui_list_snapshots, and imgui_save_snapshot, though it doesn't explicitly differentiate them.

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 on when to use this tool versus alternatives, no prerequisites described, and no error/edge-case behavior disclosed. The sibling list includes related snapshot tools (load, save, list) but nothing distinguishes when deletion applies.

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