puppet_multi_scene

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

With no annotations, the description must disclose behavioral traits. It mentions generating FCPXML files per scene but does not warn about destructive actions, required prerequisites, or side effects like file creation. The mutation action is implied but not explicitly stated.

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 front-loaded with the main purpose, followed by a structured Args section. The example for scenes_json is helpful but somewhat verbose. Overall, it earns its place without redundancy.

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?

Given 4 parameters and existing output schema, the description covers input semantics well and mentions output format (FCPXML). Missing some behavioral context and output details, but enough for basic understanding.

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 coverage is 0%, so the description fully compensates with detailed parameter explanations, especially scenes_json with an illustrative example including duration format and optional cycles. rigs_json and general structure are less defined but still useful.

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 clearly states it builds a multi-scene puppet animation with presets per scene, generating one FCPXML per scene. This distinguishes it from sibling tools like puppet_animate (single scene) or puppet_build_scene (single scene building), making its purpose specific and non-ambiguous.

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 it's 'useful for storyboarding a sequence,' implying a use case, but does not explicitly contrast with alternatives like puppet_animate or puppet_build_scene for single scenes. Lacks direct when-to-use/when-not-to-use guidance.

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