delete_preset

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

With no annotations, the description carries the full behavioral burden and does add real context: a backup copy is retained (implying recoverability), and it explains the mechanism blocking cloud-preset deletion. It stops short of stating required permissions, whether the deletion is immediate, or what the response contains beyond a hint about the cloud copy location.

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?

The action is front-loaded in the first clause, which is good. The remainder is somewhat convoluted, especially the trailing 'and the answer says where it is', which restates indirectly what the sentence already implies and costs clarity.

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?

No annotations and no output schema, so the description must justify itself, and it covers the destructive-behavior and cloud-scope story well. It is still incomplete for a two-required-parameter tool: the meaning and accepted values of 'kind' are absent, and nothing tells the agent how to recover the backup copy it promises exists.

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% and both parameters are required, yet the description never mentions them. 'kind' in particular is undefined — the agent gets no hint that it selects a preset category (filament/process/printer), nor any guidance on valid values or the interplay between kind and name.

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?

Specific verb+resource: 'Delete one of your user presets'. It also draws a scope line (local presets only, not Bambu cloud presets), which separates it from cloud-side deletion. It does not explicitly contrast with nearby siblings like edit_preset or delete_object, but the resource is unambiguous.

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 when-not case is stated clearly: a cloud preset cannot be deleted here, because Bambu Studio would re-download it. However, the alternative is described only as 'its own Delete' with a pointer to 'the answer' rather than naming a concrete tool or workflow step, so the agent has to infer the follow-up action.

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