bambu_connect_import_file

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

Annotations only give the generic mutating/open-world profile, so the description carries real weight here: it discloses the dependency on a signed-in Bambu Connect app, the official URL-scheme mechanism, and the fact that this is a cloud-mode handoff rather than a print trigger. It does not describe failure behavior when the app is absent or not signed in, which keeps it short of a 5.

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, zero filler. The core action and runtime come first, and the scope-limiting caveat about printing follows immediately, which is the right ordering for an agent skimming for routing decisions.

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 three-parameter, no-output-schema handoff tool, the description covers mechanism, prerequisite app state, and the critical non-printing side effect. It stops short of saying what the call returns (e.g. whether a success signal or URL is echoed back), which would have closed the last gap.

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 all three parameters (file_path, name, version) are already documented in the schema, including accepted file extensions. The description adds no syntax, path-format, or version-string guidance beyond what the schema supplies, so the baseline of 3 applies.

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 uses a specific verb ('Open') plus a precise resource ('an existing G-code or sliced 3MF file') and names the target runtime (Bambu Connect via its URL scheme). The clause 'does not start printing by itself' preemptively separates it from the large cluster of print-oriented siblings such as print_3mf and start_print.

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?

It makes the use case clear (handing an already-sliced file to the local Bambu Connect app) and states the key negative case (it will not begin a print). It does not explicitly route the agent to a named alternative when actual printing is desired, leaving that inference to the sibling list.

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