Create Cocos Project

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

With no annotations, the description must disclose behavioral traits. It mentions creation and optional additions but fails to note side effects like overwriting an existing project (overwrite defaults to false), or what happens if creatorPath is invalid. No mention of error conditions or required dependencies.

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 20-word sentence that efficiently conveys the tool's core function and optional features. Every part earns its place without unnecessary 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?

Given 10 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the return value, prerequisites (e.g., Cocos Creator installation), or how this tool relates to siblings like cocos_local_create_minigame_skeleton (whether it calls that internally).

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 low (20%), and the description adds minimal parameter context. It hints at createSkeleton and installEditorBridge via 'optionally adding Codex mini-game skeleton scripts and the editor bridge,' but does not explain projectRoot, scenePath, templateName, or overwrite behavior beyond 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 clearly states the tool creates a local Cocos Creator 3.8 project from a built-in template, with optional additions. It uses a specific verb ('Create') and resource ('local Cocos Creator 3.8 project'), and the optional features (Codex mini-game skeleton and editor bridge) distinguish it from sibling tools like cocos_local_create_scene_from_template.

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 description implies usage for setting up a new Cocos project, but it lacks explicit guidance on when to use this tool vs. alternatives like cocos_local_create_minigame_skeleton or cocos_local_open_project. No 'when not to use' or 'if you need X, use Y instead' instructions are provided.

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