create_camera_rig_asset

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description still adds real value beyond them by spelling out what idempotency means ('returns the existing asset') and by disclosing the Experimental status and the return payload, which matters since there is no output schema.

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?

Two compact statements with zero filler; the core action and its asset class are front-loaded, followed by the idempotency caveat and return shape. Nothing could be removed without losing information.

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 creation tool with no output schema, the description usefully supplies the return fields and idempotent behavior, and annotations cover the mutability profile. It is slightly incomplete on failure modes (e.g. invalid package_path) and on the creation workflow relative to sibling rig-building tools.

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%: both name (required) and package_path (with its default '/Game/Cameras') are documented in the schema. The description adds no parameter-level detail at all, 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 and resource ('Creates a UCameraRigAsset') and qualifies it with the subsystem ('Gameplay Camera System, Experimental'). This distinguishes it from sibling creators like create_camera_asset or create_camera_rig_crane/rail, though it never explicitly contrasts with them, so it falls just short of a 5.

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?

There is no when-to-use guidance, no ordering hints (e.g. that rig nodes/assets are built afterwards via build_camera_rig), and no mention of prerequisites or alternatives. The agent must infer all routing from the name alone.

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