copy_fixtures_to_looks

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

No annotations, so the description carries full burden. It does disclose real behavioral traits — atomicity and undo/redo support — which is valuable. But it omits failure modes (what if a fixture is absent from a target look), whether existing target values are overwritten, and permission requirements, all significant for an unannotated mutation tool.

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?

Three short sentences, front-loaded with the core action, followed by behavior and use case in descending priority. The trailing "efficiently" is mild filler, but there is no real padding.

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 3-parameter mutation tool with no annotations and no output schema, the description covers purpose, atomicity, and undo/redo but leaves failure semantics and overwrite behavior unstated. Adequate but with clear gaps an agent would want filled.

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 all three parameters are documented in the schema itself, including the constraint that fixtures must exist in the source look. The description adds no syntax, ordering, or ID-format detail beyond that, so the baseline 3 applies.

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 with clear scope: copy fixture channel values from one source look to many target looks. This distinguishes it implicitly from add_fixtures_to_look (structure vs values) and bulk_update_looks, though it never names a sibling to make the distinction 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?

"Useful for propagating lighting changes across multiple looks efficiently" implies the use case but gives no explicit when-to-use conditions or contrast with add_fixtures_to_look / bulk_update_looks. An agent must infer the routing rather than being told.

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