Delete preset

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

Beyond the annotations (destructiveHint: true), the description adds refusal behavior for system/current presets and the required type. It also notes the feature-flag prerequisite '[needs preset-CRUD build]' which is useful operational context. Nothing contradicts the annotations.

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 description is concise, front-loaded, and every clause adds value. The main purpose is stated first, followed by constraints and the feature note. No unnecessary filler.

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 simple delete operation with two parameters, the description covers the essential behavioral constraints (refusals and allowed types) and the destructive nature is already in annotations. It could have indicated the return/error behavior on refusal, but this is not critical for a basic delete.

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 compensates by explaining the 'type' parameter's allowed values (print|filament|printer). The 'name' parameter is implicitly the preset's name, and the description's focus on USER preset clarifies its scope. This is a solid addition beyond the bare schema.

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?

The description clearly states the action ('Delete') and resource ('USER preset'), and distinguishes this from system presets and the currently-selected preset. It also specifies the allowed types (print|filament|printer), which uniquely identifies this as the preset-deletion tool among siblings like delete_object.

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 description gives explicit restrictions: system presets and the currently-selected one are refused. It also lists the valid type categories. While it doesn't name alternative tools, it clearly delimits when the tool can and cannot be used.

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