backup_preset

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description adds that only the stored copy is exported and that output is a Mooer Studio .preset file over USB. It does not say what happens if the target file already exists (overwrite?), whether USB must be connected, or whether the preset slot must be selected first. Note that writing a file to USB is a filesystem side effect that sits slightly awkwardly with readOnlyHint, though it does not modify device state.

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 front-loaded sentence of about fifteen words with zero filler; the verb, scope and output target all appear immediately.

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 export tool with no output schema, the description covers the essential action and artifact, but it leaves the return value (path written? success flag?) and the preset parameter's meaning unstated. Adequate to attempt a call, not complete enough to predict the result confidently.

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 coverage is only 50%: 'file' is documented in the schema as the output path with a data-directory default, but 'preset' has only a 1-80 integer range and no explanation. The description does not compensate by saying that 'preset' is the slot number/index or what happens when 'file' is omitted or points to an unwritable USB path.

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?

Names a specific verb and resource (export one preset) plus the output artifact type (.preset file) and transport (USB), which separates it from save_preset and list/get siblings. It only implicitly distinguishes itself from backup_all_presets via the words 'one preset', rather than naming the sibling outright.

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 phrase 'stored version' implies this exports persisted preset data rather than live edits, which is a useful usage cue, but there is no explicit when-to-use/when-not guidance or reference to alternatives such as backup_all_presets or restore_preset. The agent must infer the choice from the name and the word 'one'.

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