Create Cocos Component Script

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

No annotations are provided, so the description must fully convey behavioral aspects. It mentions the script includes ccclass, typed properties, and lifecycle stubs, but does not disclose side effects (e.g., file creation, overwrite behavior), error conditions, or required permissions. Critical gaps exist for a creation tool.

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 15-word sentence that immediately conveys the tool's purpose. No extraneous information is present, making it efficient and front-loaded.

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 has 8 parameters, no output schema, no annotations, and 38% schema coverage, the description is too sparse. It omits essential context about parameter usage, outcome, and error handling, leaving significant gaps for the agent.

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 only 38%, and the tool description does not add parameter-specific details. It hints at lifecycle and properties but fails to explain parameters like overwrite, scriptPath, projectRoot, or baseClass. The high-level summary does not compensate for the low schema coverage.

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 specifies 'Create a Cocos Creator 3.8 TypeScript Component script with ccclass, typed properties, and lifecycle stubs.' It clearly states the verb (Create) and the resource (Component script), and distinguishes from sibling tools that create other Cocos artifacts like scenes or projects.

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 creating component scripts, and the tool name and title make it clear. However, it does not explicitly state when to use this tool versus alternatives like cocos_local_create_scene_from_template, but the context of sibling tools and the title provide sufficient clarity.

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