project_open

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

With no annotations, the description takes on the disclosure burden. It surfaces a genuinely important behavior: .aup3 inputs cause an interactive conversion prompt that is unsafe to trigger over MCP. It doesn't detail what happens to the current project on open, but the main safety-relevant trait is disclosed.

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 tight and front-loaded: the core action and format appear first, followed by a necessary safety warning, then one-line argument documentation. No filler.

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 one-parameter open tool, the description covers the essential invocation detail (absolute .aup4 path) and the major edge case (.aup3 conversion prompt). It does not describe return values or whether the current project is replaced, but that is less critical for making the call.

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%, and the description compensates by specifying that 'path' must be an absolute path to a .aup4 file. It also implies the file must exist ('existing'), adding meaning beyond the bare string schema.

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 specifies the action ('Open'), the resource ('existing Audacity project file'), and the supported format ('.aup4'), which is unambiguous. It does not explicitly name a sibling alternative, but the format and 'existing' wording set it apart from project_new and project_import_audio.

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 provides a concrete when-not: .aup3 files must not be used because they trigger an interactive conversion prompt unsafe for MCP. It does not explicitly route to an alternative tool, so it stops short of a full usage-guide comparison.

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