Switch moveset

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive, closed-world), so the bar is lower. The description goes beyond them by disclosing exactly what is mutated (SaveData.MovesetIndex and MCP state) and that the tool emits executable Luau that clicks the UI live — non-obvious side effects an agent should know about.

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?

Two tight sentences with no filler; the persist-and-return behavior leads and identifier guidance follows. Slightly dense but every clause carries information.

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 single-parameter mutation tool with no output schema, the description covers purpose, persisted state, and the Luau return value. Minor gaps remain (behavior on ambiguous or invalid identifiers, whether an executor is assumed), but nothing critical for correct invocation is missing.

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 description coverage is 100%, so the sole 'moveset' parameter is already fully documented in the schema. The description restates the same accepted forms (name substring, InternalName, 1-based index) without adding new syntax or disambiguation rules, so the 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?

States a specific verb (persist/switch) and resource (moveset), plus the two concrete effects: writing SaveData.MovesetIndex + MCP state and returning executor-ready Luau that clicks the Movesets UI entry. This clearly separates it from siblings like reanim_list_movesets, reanim_create_moveset, and reanim_get_current_moveset.

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?

Points at reanim_list_movesets as the source of valid identifiers, which implicitly tells the agent to list before switching. However, it never states when to prefer this over alternatives such as reanim_random_moveset, nor any preconditions or exclusions — usage is implied rather than explicit.

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