project_import_audio

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does reveal the state requirement (open project) and acceptable audio formats, which is useful. However, it does not mention whether the operation is undoable, whether the audio file is copied or referenced, or what happens with an invalid path.

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 front-loaded with the core purpose, followed by the essential prerequisite and parameter detail. Every sentence earns its place, and there is 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 import tool with no output schema, the description covers the essential aspects: what it does, when it can be called, and what the path parameter requires. A small gap is that it does not indicate whether the command returns status information or whether the import is asynchronous, but the provided context is sufficient for correct invocation.

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 only names the parameter 'path' with no description, so the description fully compensates by explaining it must be an absolute path and listing supported formats (wav, mp3, ogg, flac, etc.). This is precisely the semantic detail an agent needs.

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 into the current project as a new track.' This gives a specific verb, resource, and result, and it is distinguishable from sibling tools like project_export_audio or transcribe_to_file.

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 explicitly states the critical prerequisite: a project must already be open, and it names the tools to use first (project_new or project_open). It provides clear context for when this tool is appropriate, though it does not discuss exclusions or alternative import paths.

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