open_project

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

The description offers no behavioral detail beyond what the annotations already indicate (destructiveHint: true). It does not mention that opening a new project may discard unsaved changes, affect the current session, or have other side effects. The description adds no extra context, so the agent relies solely on the annotation flag.

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?

The description is extremely concise—two sentences covering purpose and the single parameter. It is front-loaded with the action and includes the necessary detail for the argument. No wasted words or unnecessary elaboration.

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 open operation, the description is minimally adequate: it states what it does and how to specify the file. However, given the destructive hint, it could mention consequences like overwriting the current project or losing unsaved work. There is also no mention of return values or success/failure behavior, though the lack of an output schema reduces the burden.

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?

The schema provides only a string type for 'path', but the description adds meaningful semantics: it specifies a full path to an .rpp file. This clarifies the expected format and file extension, which is helpful beyond the bare schema. Since schema coverage is 0%, this compensation is valuable.

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 clearly states the tool opens a REAPER project file, which is a specific action on a specific resource. It does not explicitly differentiate from sibling tools like create_project or save_project, but the action is distinct enough that the purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, conflicts, or situations where other tools (like create_project or save_project) would be more appropriate. The agent is left to infer usage from the name and description.

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