xr18_snapshot_load

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

There are no annotations, so the description must disclose behavioral traits itself. It does not mention that recalling a snapshot overwrites current mixer state, whether the operation is destructive or reversible, or what prerequisites or errors apply.

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 short sentence contains the action, target resource, and parameter range with no filler. The information is front-loaded and every word contributes.

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 one-parameter command, the description covers the core invocation details. However, with no annotations and no output schema, it omits usage context and side effects, so it is only minimally 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?

The schema only declares slot as an integer with no description, but the description adds the essential valid range of 1-64. For a single required parameter this is sufficient guidance for correct invocation.

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, recall, and a precise resource, snapshot slot, with a valid range of 1-64. This differentiates the operation from sibling tools like snapshot_save or snapshot_delete based on the action alone.

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 is given about when to use this tool versus snapshot_save, snapshot_delete, snapshot_set_scope, or snapshot_set_name. The agent is left to infer the intended use from the tool name and one-line description.

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