Open Cocos Project

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

Description only mentions launching and optional waiting. No details on behavior like whether it checks for existing instances, blocking nature, or side effects. Annotations are absent, so description carries the burden but fails to disclose important traits.

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?

Single sentence, front-loaded with main action. However, it is too brief for a complex tool, sacrificing necessary detail.

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?

With no annotations, no output schema, and 6 parameters, the description is severely incomplete. It lacks return value info, error conditions, and parameter roles.

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 coverage is 0% and the description provides no explanation of any of the 6 parameters (port, dryRun, timeoutMs, creatorPath, projectRoot, waitForBridge). Agents cannot infer meaning.

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 'Launch Cocos Creator 3.8 for a local project' with the verb 'Launch' and resource. It distinguishes from siblings like 'open_scene' which opens an existing scene, but does not explicitly contrast with other tools.

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 on when to use this tool vs alternatives (e.g., when to also use 'waitForBridge'). No mention of prerequisites or exclusions.

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