createCameraRig

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

No annotations are provided, so the description carries the full burden. It does disclose the compound structure it builds (two nulls plus a parented camera), which is genuine behavioral context. However, it omits mutation side-effects, whether it needs an active composition, undo behavior, and what it returns.

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 with no wasted clauses; the core action and its components come first. Minor marketing filler ('professional industry-standard', 'effortless') slightly dilutes it but does not hurt scanability.

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 five-parameter creation tool with no output schema and no annotations, the description explains what is built but says nothing about the return value (e.g. the created rig objects) or the composition prerequisite implied by the compName default. Adequate but with a real gap.

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% across all five parameters, so the schema already documents rigName, compName, distance, cameraName, and targetPosition with defaults. The description adds no parameter-level detail, so the baseline 3 is appropriate.

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 (Create) and resource (3D Camera Rig), and names the concrete output structure — Target Null, Orbit Null controller, and parented Camera. It implicitly distinguishes from createCamera (single camera) and createNullObject, but never names those siblings, so the differentiation is inferential rather than explicit.

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 mentions the benefit (orbit and gimbal-lock-free animation) but gives no explicit when-to-use guidance and never points to alternatives like createCamera, createNullObject, or applyCameraMove. The agent must infer that this is for rig-based orbit work.

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