raw_open

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

With no annotations, the description carries the burden and does disclose important behavioral uncertainty: it 'may open a dialog or change project state' and tells the agent to inspect the command name first. It does not detail specific side effects or recovery steps, but the caution is meaningful.

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 compact and each clause adds value: purpose, no-argument nature, and behavioral warning. The 'Open: Open' prefix is mildly redundant but does not hurt clarity.

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?

Core invocation is clear for a zero-parameter tool, but the description leaves ambiguity about what happens after the potential dialog, what exactly 'inspect the command name first' requires, and how raw_open relates to higher-level open/project siblings. No output schema or return behavior is described.

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 input schema is empty and the description explicitly says this is a no-argument action, so parameter explanation is unnecessary. This matches the baseline for a zero-parameter tool.

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 states a specific action: open an audio file, list of files, or project, and adds a key distinguishing constraint—this is a static no-argument Audacity action. It is clear, but it does not explicitly differentiate raw_open from sibling commands like project_open or raw_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?

Usage is implied: this is a low-level, no-argument raw command, and the warning to 'inspect the command name first' hints at caution. However, it never explicitly states when to choose raw_open over alternatives or when not to use it.

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