Apply Cocos Scene Blueprint

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

With no annotations, the description must disclose behavioral traits. It mentions applying through the editor bridge but does not describe side effects, destructiveness, or prerequisites beyond 'currently open scene'. This is minimal and leaves the agent guessing about safety.

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 sentence, which is concise but lacks structure. It does not front-load key information or break down the tool's operation. For a tool with 8 parameters, this is under-specified.

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 8 parameters, no annotations, and no output schema, the description is severely incomplete. It omits the process, side effects, prerequisites (like editor bridge installation), and parameter guidance. The agent cannot use this tool effectively without additional context.

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 0%, and the description mentions no parameters. The agent is left with only parameter names (e.g., projectRoot, blueprintPath) which may be ambiguous. The description should add meaning to at least some parameters.

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 (read and apply) and the resource (generated scene blueprint JSON to the currently open Cocos scene) with specific verb and resource. It differentiates from sibling tools like cocos_local_create_scene_from_template or cocos_local_open_scene.

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 vs alternatives like cocos_local_create_scene_from_template. There is 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.