raw_import_audio

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

With no annotations provided, the description must disclose behavioral traits itself. It does state 'May open a dialog or change project state', which hints at side effects, but it is non-committal and does not specify the exact behavior or whether it is destructive. The extra advice to 'inspect the command name first' is unclear and does not add substance. This is adequate but minimal.

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 a single sentence with the core action front-loaded, followed by a technical note and a caution. It is concise and well-structured. The caution 'inspect the command name first' is slightly cryptic but does not bloat the text. It earns a 4 for being appropriately sized and clear.

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?

Given that this is a no-argument command with no output schema, the description covers the essential action but leaves out details like what file dialog appears, how the audio file is selected, or potential prerequisites. The warning to 'inspect the command name first' suggests that more verification might be needed, which is a gap. It is complete enough for a basic call but not fully self-contained.

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 tool has zero parameters and schema coverage is effectively total since there are no properties. There is nothing for the description to add about parameters. The baseline for zero-parameter tools is 4, and the description does not contradict or fail to cover anything in this regard.

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 action: 'Import an audio file as a new track.' It identifies the resource (audio file) and the expected outcome. It does not explicitly contrast with the sibling 'project_import_audio', but the purpose is unambiguous. The 'Static no-argument Audacity action' wording adds a technical detail that helps identify the tool's nature.

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 guidance on when to use this tool versus alternatives. The warning 'inspect the command name first' is vague and does not explain conditions that would favor this tool over others like project_import_audio or raw_open. It lacks any explicit when-to-use or when-not-to-use information.

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