create_project

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state what happens to the currently loaded project, whether unsaved work may be discarded, or how creation affects the application/project state. The parameter ranges are useful but do not cover these side effects.

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 brief one-sentence purpose followed by a compact argument list. Every line in the Args section adds range/semantic information not present in the schema, and the purpose statement is front-loaded. No wasted words.

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?

All parameters are covered and an output schema exists, so return-value documentation is not needed. However, the description omits important contextual behavior about replacing/discarding the current project and when to prefer this over load_project or the individual setter tools. This leaves the agent with a moderate but meaningful gap.

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 description coverage is 0%, but the description compensates fully by documenting every parameter with meaning and valid ranges (e.g., bpm 10-999, master_volume 0-200, master_pitch -12 to +12). This adds real value beyond the bare schema defaults.

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 verb ('Create'), a clear resource ('a new empty LMMS project'), and the word 'empty' distinguishes it from loading or saving projects. It clearly separates this tool from siblings like load_project and save_project.

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 usage is implied: create a fresh project, rather than load an existing one or adjust settings post-creation with set_tempo/set_time_signature/set_master_volume. However, there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives, so the agent must infer from sibling names.

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