generate_bezier_camera_path

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

No annotations are provided, so the description must carry the full behavioral burden. It clearly states that the tool writes to a .tscn file and adds Path3D/Curve3D nodes, which is the core behavior. However, it doesn't disclose potential side effects like overwriting existing nodes, whether the file must already exist, or if any permissions are required. The description covers the primary action but leaves important edge cases unstated.

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. It starts with a concise summary of the tool's purpose, then specifies the waypoint dict format, and then lists each argument with clear explanations. Every sentence adds value; there is no filler or repetition. The length is appropriate for the complexity of the tool.

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?

For a tool with six parameters and nested waypoint structures, the description covers the essentials: parameter meanings, defaults, and even tension usage guidance. An output schema exists, so return values are handled externally. Minor gaps include whether the scene file must pre-exist or what happens if nodes with the same name already exist, but these are edge cases that don't impede correct invocation in most scenarios.

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 schema has zero description coverage, so the description is the only source of parameter meaning. It explains every parameter: scene_path (absolute path), path_node_name (naming example), waypoints (with required 'position' and optional 'tilt' fields), add_path_follow, add_camera, and tension (with range -1.0 to 1.0 and usage guidance for sweeping vs. tight moves). This fully compensates for the missing schema descriptions.

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 opens with a precise statement: 'Calculate Catmull-Rom bezier handles from world-space waypoints and serialize them as Path3D + Curve3D node blocks in a .tscn file.' This gives a specific verb, resource, and output format. It also lists supported moves (arc pans, dolly zooms, etc.), which clarifies the tool's scope and differentiates it from generic scene manipulation tools, though it doesn't explicitly name sibling tools. The purpose is unmistakable.

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 context by describing the supported camera moves and the nature of the output, but it never explicitly tells the agent when to choose this tool over alternatives like build_camera_switcher_timeline or inject_lookat_tracking. There is no 'use this instead of X' guidance, so the usage is implied rather than explicit.

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