list_user_presets

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

With no annotations, the description carries the behavioral burden and does well: it discloses that results include inheritance, changes, cloud membership, and reverse dependencies, and warns that cloud presets can only be deleted or renamed in Bambu Studio. It stops short of explicitly stating read-only safety or permission requirements, which are implied by 'list' but not stated.

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, front-loaded with the core action and scoped parameter, then the return contents and sibling alternative. The density is high but every clause contributes necessary context.

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 output schema exists, so the description must convey return meaning; it does by describing inherited preset, changed settings, cloud status, and dependent presets. For a single optional parameter list tool, this is complete enough for correct invocation.

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 0% and the schema only declares kind as an unconstrained string with default empty. The description compensates fully by naming the allowed values filament, process, printer and explaining that empty means all.

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: list the user's own Bambu Studio presets, scoped by kind. It also explicitly distinguishes this from search_presets for system presets, so an agent can select between them without opening schemas.

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?

Explains that kind filters to filament, process, or printer, and empty returns all. It also names the alternative search_presets for finding system presets too, giving clear routing guidance.

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