export_sample

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 largely covered. The description adds the useful detail that output goes to a USB file and names the formats, but is silent on overwrite behavior, path resolution, and what happens if the USB target is absent.

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 with no filler, appropriately sized for a simple export action, though the telegraphic format shorthand makes it slightly cryptic rather than informative.

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?

With 3 parameters, 0% schema description coverage, and no output schema, the definition should explain the kind enum, the file parameter, and what the call returns or where the file lands. None of that is present, leaving real gaps for a tool whose whole contract is 'write this data to that file'.

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 0% across three parameters, so the description must carry the load and largely fails: 'kind' and its four enum values are never explained, and 'file' is only implied by '(USB)' with no indication whether it is a path, filename, or optional default. Only 'slot' is loosely conveyed by 'sample slot'.

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 ('Save a sample slot to a file') plus the destination medium (USB) and target formats, so an agent can tell it dumps slot data to disk. It is slightly blurry on whether 'sample' means a preset slot or sample file, and the listed extensions (.gir/.gnr/.preamp) do not map cleanly to the 'kind' enum (drive/pre-amp/entire-amp/cab).

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 on when to export versus using list_samples, import_sample, or backup_preset/backup_all_presets, which are plausible alternatives in the sibling set. No prerequisites (USB mounted? file path required? overwrite allowed?) are stated.

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