load_preset

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

Adds substantial behavior beyond the annotations: only differing parameters are written, the current board is auto-saved first, the load is one undo step, and confirmation is always required. These details are not present in the annotations and meaningfully inform the agent about side effects and reversibility.

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 sentences, no filler. The first sentence front-loads the core purpose and partial-write behavior; the second covers all operational prerequisites. Every clause earns its place.

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 two-parameter tool with no output schema and annotations already marking it destructive, the description covers everything needed to invoke it correctly: what it does, the confirmation requirement, the auto-save safety net, and undoability. No critical operational detail 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?

With 0% schema description coverage, the description must compensate, and it does: 'Restore a saved preset' implies name selects the preset, and 'Always needs confirm' directly indicates that the confirm parameter must be true (despite its schema default of false). It does not explicitly name the parameters but gives enough functional meaning for both.

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 and resource ('Restore a saved preset to the mixer') and adds a crucial distinguishing behavior ('only differing parameters are written'). Clearly separates it from save_preset, list_presets, and snapshot_load by indicating this is a targeted partial restore, not a full snapshot reload.

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?

Provides a strong prerequisite: 'Always needs confirm,' which tells the agent the confirm parameter must be set to true. It also mentions the auto-save and undo-step effects, giving the agent enough context to decide when this destructive operation is appropriate. It does not explicitly name alternative tools or exclusions, so it falls short of a 5.

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