demo_edm_project

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

No annotations provided, so description carries full burden. Discloses that it creates tracks with ReaSynth and MIDI patterns, and that clean_first parameter wipes existing MIDI and markers. Missing details about whether it opens a new project or affects current state, but overall adequate given simplicity.

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?

Front-loaded with core purpose, then usage example, then track listing, then parameters. Each sentence is purposeful, no fluff. Highly efficient for the amount of information conveyed.

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?

With only 2 optional parameters and no output schema, the description covers all essential aspects: what it creates, how to use it afterward, and parameter details. Complete enough for an agent to invoke correctly.

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 coverage is 0%, so description must add meaning. Describes clean_first as 'wipe existing MIDI + markers first' and bpm with default 140 and explanation of matching half-time feel. This adds significant value beyond the schema's type/default fields.

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?

Clearly states specific verb 'scaffold' and resource 'minimal EDM test project' with 7 tracks. Lists tracks and MIDI. Distinguishes from siblings which are individual operations (track_create, midi_insert_notes, etc.) by creating a whole project. No ambiguity.

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?

Explicitly states when to use: to verify end-to-end workflow of engine_mix, engine_master, setup_sidechain. Provides concrete follow-up commands. Does not explicitly mention when not to use or alternatives, but the context is clear for a test project tool.

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