open_project

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

With no annotations, the description carries the full disclosure burden and does add real value: it explicitly declares the source file is never mutated and warns that some content may not be carried over ('what could not be carried over'). It omits what happens to any currently-open project state, what errors occur on an invalid/corrupt path, and whether loading has side effects on the session.

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?

Three short sentences with no filler; the core action and accepted format come first, followed by the immutability guarantee and the return-behavior note. Every sentence carries distinct information.

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?

The absence of an output schema is partly offset by the description naming the return payload (project summary plus un-carried-over items). For a load operation that mutates application state, the description should say whether the current project is replaced or unsaved work is affected, and what happens on failure.

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% for the single 'path' parameter, so the description must compensate, and it does: it constrains path to a .3mf file saved by Bambu Studio or downloaded from MakerWorld, narrowing the valid input domain beyond a bare string. It does not specify absolute vs relative paths or whether the file must be local, keeping it below a 5.

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 (open) and a specific resource (a .3mf authored by Bambu Studio or MakerWorld), which pins down both the action and the accepted input format. It contrasts with save_project, but does not disambiguate from the similarly-named sibling open_in_bambu_studio or from get_project, which an agent could reasonably confuse with a load operation.

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 line 'The file is never modified: save_project writes a new file' implicitly tells the agent to use save_project for persistence rather than this tool. However, there is no explicit statement of when to prefer this over new_project, get_project, or open_in_bambu_studio, so the routing guidance is inferred rather than stated.

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