trackCameraToLayer

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

No annotations are provided, so the description carries full burden. It explains what each tracking mode does behaviorally (aim, follow offset, lock focus), but omits whether it creates expressions/constraints, whether it is reversible, what permissions or preconditions are required, and what happens to prior tracking links.

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?

A single front-loaded sentence establishing the action and then the three modes. Efficient, though the parenthetical glosses make it slightly run-on rather than crisply itemized.

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 6-parameter rigging tool with no annotations and no output schema, the description covers purpose and mode semantics but leaves out preconditions, side effects on existing tracking, and error behavior, so an agent lacks enough to invoke it confidently in edge cases.

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 100%, so the schema already documents compName, cameraName, cameraIndex, targetLayerName, targetLayerIndex and the trackMode enum in detail. The description's mode gloss largely duplicates the enum description, adding no syntax or precedence detail (e.g. name vs index).

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?

States a specific verb and resource: 'Link a 3D camera to track a target layer', and enumerates the three tracking modes. The purpose is unambiguous, though it doesn't explicitly distinguish itself from related camera siblings like createCameraRig or setCameraProperties.

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 three modes are presented as alternatives, which implicitly guides mode selection, but there is no guidance on when to use this tool versus createCameraRig, applyCameraMove, or setCameraProperties, and no prerequisites (e.g. camera and target layer must already exist).

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