snapshot_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds useful scoping detail (only named snapshots, limited to 1-64), which helps an agent understand exactly what will be returned. It does not discuss auth or rate limits, but those are less relevant for a read-only, non-destructive list 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?

A single, tightly worded sentence that leads with the verb and resource, immediately clarifying scope. No filler or redundant details.

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 simple, parameterless tool with no output schema, the description is mostly sufficient, but it does not specify the return shape (e.g., list of names, slot numbers, or pairs). Since the agent must call this tool without knowing the output format, this is a notable gap. The description covers the input and scope but not the expected response.

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?

There are zero parameters, and schema coverage is 100% (vacuously). The description correctly specifies the complete parameter set, so the baseline of 4 applies without needing further parameter explanation.

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 specific verb ('List') and resource ('the mixer's internal snapshots (slots 1-64) that have a name'), making it clear what the tool does. This distinctly separates it from snapshot_save, snapshot_load, and list_presets, which target different resources or operations.

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 implies the use case clearly: when you need to enumerate named snapshots in slots 1-64. It does not explicitly mention alternatives or when not to use it, but the tool's name and clear scope provide sufficient context without exclusions.

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