cocos_scaffold_camera_follow

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

With no annotations provided, the description carries the full burden and excels by disclosing key behavioral traits: it generates a file with specific properties (e.g., target tracking, smoothing logic), mentions performance details ('Zero per-frame allocation'), handles edge cases ('null-checks target each lateUpdate'), and describes the return format. This goes beyond basic functionality to include implementation nuances.

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 well-structured and front-loaded with the main purpose, followed by property details and behavioral notes. It is appropriately sized with no wasted sentences, though it could be slightly more concise by integrating some details more tightly. Every sentence adds value, such as explaining smoothing logic and memory usage.

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 complexity of generating a camera-follow script with multiple behavioral aspects, no annotations, and no output schema, the description is largely complete: it covers purpose, properties, performance, edge cases, and return values. However, it lacks information on the input parameters, which is a minor gap in an otherwise thorough explanation.

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 input schema has 2 parameters with 0% description coverage, and the tool description does not mention or explain these parameters at all. While the description details the generated script's properties (e.g., target, offsetX), it fails to add meaning to the actual input parameters (project_path, rel_path), leaving them undocumented and unclear in context.

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's purpose: 'Generate CameraFollow.ts — attach to the Camera node to track a target with deadzone + frame-rate-independent smoothing + optional world bounds.' It specifies the verb ('Generate'), resource ('CameraFollow.ts'), and distinguishes from siblings by focusing on camera-follow functionality, unlike other scaffold tools for audio controllers, enemy AI, etc.

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 provides clear context for when to use this tool: 'attach to the Camera node to track a target.' It implies usage for camera tracking in game development. However, it does not explicitly state when not to use it or name alternatives among siblings, such as other camera-related tools like 'cocos_add_camera'.

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