create_project

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

No annotations exist, so the description must fully disclose behavior. It only says 'create a new project' without specifying what happens to the current project, whether a file is saved, or if any side effects occur. This is inadequate for a tool that likely modifies the application state.

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 extremely concise (5 words, one sentence) and front-loaded with the key action. However, it is so minimal that it sacrifices completeness for brevity, which slightly reduces the score from a perfect 5.

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 the tool's simplicity (one optional parameter, no output schema, no annotations) and the large set of sibling tools, the description is insufficient. It fails to explain what 'creating a project' entails (e.g., does it replace the current project? Is it saved to disk? What is the return value?). This leaves the agent with critical gaps.

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 covers the single parameter with 100% description coverage ('Optional project name'). The description adds no additional meaning beyond the schema, so it meets the baseline of 3 but provides no extra value.

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 clearly states the action ('create') and resource ('new After Effects project'), distinguishing it from siblings like 'open_project' or 'save_project' by implying a new project. However, it does not explicitly differentiate from other creation tools (e.g., 'create_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?

No guidance is provided on when to use this tool versus alternatives such as 'open_project', 'save_project', or 'close_project'. The agent receives no context on prerequisites, workflow order, or when creation is appropriate.

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