open_project

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is known; the description usefully adds that the project is copied into an isolated workspace, implying the original is preserved. It still omits what happens to an existing workspace, whether Studio must be running, and what the result looks like.

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?

A single front-loaded sentence with no filler; the core action ('Copy a saved 3MF') comes first. The trailing 'through Studio' clause adds ambiguity rather than value, keeping it from a 5.

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 four-parameter mutating tool with no output schema and no schema descriptions, the description should carry more weight than it does. It establishes the isolation/copy semantics but leaves the profile-override behavior and observable outcome under-specified.

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%, so the schema gives no parameter meaning at all and the description must compensate. It only gestures at 'explicit profiles' and a saved 3MF, without clarifying that machine_profile, process_profile, and filament_profiles are optional overlays or how they relate to path.

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 specific actions on a definite resource: copying a saved 3MF into an isolated workspace, or importing a model with explicit profiles. It is clear what the tool does, but it never distinguishes itself from siblings such as open_in_studio or inspect_project, and the dual 'or' behavior leaves which mode applies to the agent.

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?

There is no explicit when-to-use, no when-not-to-use, and no named alternative despite siblings like open_in_studio and export_project that a caller could confuse with this. The two modes hint at scenarios but never say which parameters or conditions select them.

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