list_slicer_profiles

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

With no annotations, the description must carry the safety profile, and it does signal a non-destructive read that neither slices nor talks to hardware. However, it says nothing about whether results are cached, how large the catalog can be, what 'dependency evidence' concretely contains, or how errors surface when a preset is missing.

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, both earning their place: the first states what is returned, the second states the boundary. The core capability is front-loaded and there is no filler or restatement of the tool name.

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 five optional, fully documented parameters and no annotations, this is a simple read tool and the description is nearly sufficient. The remaining gap is return shape: there is no output schema, and 'dependency and declared compatibility evidence' is not explained in enough detail for an agent to know what fields come back.

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 100%, so the schema already documents kind, limit, query, offset and machine_preset with enums, defaults and bounds. The description adds only the notion that results carry 'declared compatibility evidence', which hints at what machine_preset evaluates, but it does not explain the filter/check interplay or sort order beyond the 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 gives a specific verb and resource ('List installed Bambu Studio printer, process and filament presets') and names the payload attributes (dependency and declared compatibility evidence). It also carves out scope negatively ('Does not slice or contact a printer'), which separates it from slice_stl/slice_with_template, but it never names the nearest catalog-like siblings such as slicer_info, get_slice_settings or list_templates.

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?

Usage is only implied: an agent can infer this is the discovery step before slicing or compatibility checks, and the negative clause rules out slicing. There is no explicit 'use this when... / use X instead' routing, and no mention of prerequisites such as Bambu Studio being installed or presets being present.

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