New project

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

While the annotations already indicate destructiveHint=true, the description adds valuable context by stating it 'replaces the current project,' making the exact destructive behavior explicit. It also implies a reset to a demo-ready template, which is useful beyond the generic annotation.

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, front-loaded sentence with no unnecessary words. It states the action, the result, and the key side effect (replacement) efficiently.

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 destructive creation tool with one optional parameter and no output schema, the description is minimally adequate. It explains the core action and side effect, but does not detail what 'demo-ready' entails, default behavior when 'name' is omitted, or what the tool returns. Given the presence of annotations, this is acceptable but not thorough.

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 schema has one optional 'name' parameter, but the description does not explain its purpose or how it affects the created project. With 0% schema description coverage, the description should compensate but does not, leaving the semantics of 'name' unclear.

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 uses a specific verb ('Create') and resource ('fresh demo-ready audio project'), and explicitly notes that it replaces the current project. This clearly distinguishes it from sibling tools like set_project or import_project, which modify or import rather than create anew.

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 phrase 'fresh demo-ready' implies the use case of starting a new demo project, but there is no explicit guidance on when not to use this tool or how it compares to alternatives like set_project or import_project. Usage is implied rather than clearly stated.

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