project_export_audio

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

No annotations provided, so description carries full burden. Discloses critical behavioral constraints: mandatory user notification requirement, format determination logic (extension-based), and filesystem constraints (subfolder requirement). Lacks disclosure on overwrite behavior, blocking/synchronous nature, or error handling.

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?

Well-structured with front-loaded purpose, followed by mandatory constraints in ALL CAPS for emphasis, then examples, then parameter docs. Lengthy but justified by critical safety constraints (preventing home directory clutter). Every sentence serves the agent's decision-making or invocation correctness.

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 no output schema and no annotations, description adequately covers the operation's side effects (file creation), constraints, and prerequisites. References related tool for default paths. Missing only explicit mention of overwrite behavior or return value description, but complete for an export operation of this complexity.

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 has 0% description coverage (only titles). Description fully compensates by documenting 'path' semantics (absolute path, extension determines format with valid examples wav/mp3/ogg/flac/aiff) and 'num_channels' (1=mono, 2=stereo with default value). Syntax and valid values clearly specified.

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?

Clear specific verb ('Export') + resource ('project audio') + mechanism ('to a file'). Explicitly distinguishes from sibling 'analyze_sample_data_export' by focusing on standard audio export, and from 'project_save' by targeting external file formats.

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?

Exceptional guidance with explicit 'ALWAYS'/'NEVER' constraints, mandatory prerequisite ('tell the user where the file will be saved BEFORE exporting'), and explicit alternative tool named ('call get_default_export_folder'). Clearly defines acceptable locations (Music, Documents, Desktop) and prohibited ones (home folder).

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