ae_new_project

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the critical destructive side effect: 'closes the current one'. This is valuable transparency for a mutating operation. It could go further by noting that unsaved changes would be lost, but the core behavioral trait is disclosed.

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?

A single sentence with zero superfluous words. The core action is front-loaded, and the crucial side effect is appended concisely in parentheses. Every word earns its place.

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 zero-parameter tool with no output schema, the description adequately covers what the tool does and its most important consequence. It is slightly incomplete in that it does not mention whether unsaved changes are saved or discarded, or what the return value indicates, but these are minor gaps for such a simple operation.

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 tool has zero parameters and schema coverage is 100%, so there is nothing for the description to clarify. Per the rubric, zero params warrant a baseline of 4. The description adds no parameter-specific detail because none is needed.

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 ('new blank After Effects project'), and the parenthetical 'closes the current one' clearly distinguishes it from siblings like ae_open_project, ae_close_project, and ae_create_composition. An agent can immediately tell this starts a fresh project rather than opening or creating a composition.

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 context is implicit: this is for starting a blank project from scratch, which is reasonably inferred from the wording. However, it does not explicitly state when to use this versus ae_open_project, ae_save_project, or ae_close_project, nor does it mention any prerequisites or exclusions. The guidance is present but only by implication.

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