list_profiles

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It does add that profiles are 'installed' (i.e., read from the local filesystem) and that filtering is by name, which is useful. It says nothing about return ordering, whether all three profile categories are returned together, or what happens when no profiles are installed.

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 short sentences with the resource and scope front-loaded and no filler. The second sentence is terse to the point of being clipped ('Filter by name'), but nothing is wasted.

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 read-only listing tool with one optional parameter and no output schema, the description covers what is listed and how to filter it. It omits the practical details an agent would want — the shape of the result (paths only vs names plus paths) and whether the filter narrows across all profile types — which leaves it merely adequate.

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%, so the description must carry the burden for the single 'search' parameter. 'Filter by name' does clarify that the parameter matches on profile name rather than path or type, but it leaves match semantics (substring vs exact, case sensitivity, whether it applies across all three profile categories) undefined.

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 names a specific operation and resource: finding installed Bambu Studio machine, process, and filament profile paths. That is clearly distinct from sibling tools like list_printers or printer_status. It stops short of a crisp verb+return statement (does it return paths only, or profile metadata too?), which keeps it from a 5.

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 states a purpose but gives no when-to-use guidance, no prerequisites (e.g., Bambu Studio installed), and no comparison to the sibling tools that also enumerate devices or resources. An agent must infer that this is the discovery step before prepare_job without being told so.

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